linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hans Verkuil <hverkuil@xs4all.nl>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
	Jan Kara <jack@suse.cz>,
	linux-media@vger.kernel.org
Cc: Hans Verkuil <hans.verkuil@cisco.com>,
	Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
	linux-mm@kvack.org, dri-devel@lists.freedesktop.org,
	David Airlie <airlied@linux.ie>, Pawel Osciak <pawel@osciak.com>
Subject: Re: [PATCH 0/9 v2] Helper to abstract vma handling in media layer
Date: Fri, 24 Apr 2015 13:07:37 +0200	[thread overview]
Message-ID: <553A23F9.1080504@xs4all.nl> (raw)
In-Reply-To: <553A2229.5040509@samsung.com>

Hi Marek,

On 04/24/2015 12:59 PM, Marek Szyprowski wrote:
> Dear All,
> 
> On 2015-04-02 17:25, Hans Verkuil wrote:
>> On 04/02/2015 05:02 PM, Jan Kara wrote:
>>>    Hello,
>>>
>>> On Tue 17-03-15 12:56:30, Jan Kara wrote:
>>>>    After a long pause I'm sending second version of my patch series to abstract
>>>> vma handling from the various media drivers. After this patch set drivers have
>>>> to know much less details about vmas, their types, and locking. My motivation
>>>> for the series is that I want to change get_user_pages() locking and I want to
>>>> handle subtle locking details in as few places as possible.
>>>>
>>>> The core of the series is the new helper get_vaddr_pfns() which is given a
>>>> virtual address and it fills in PFNs into provided array. If PFNs correspond to
>>>> normal pages it also grabs references to these pages. The difference from
>>>> get_user_pages() is that this function can also deal with pfnmap, mixed, and io
>>>> mappings which is what the media drivers need.
>>>>
>>>> I have tested the patches with vivid driver so at least vb2 code got some
>>>> exposure. Conversion of other drivers was just compile-tested so I'd like to
>>>> ask respective maintainers if they could have a look.  Also I'd like to ask mm
>>>> folks to check patch 2/9 implementing the helper. Thanks!
>>>    Ping? Any reactions?
>> For patch 1/9:
>>
>> Acked-by: Hans Verkuil <hans.verkuil@cisco.com>
>>
>> For the other patches I do not feel qualified to give Acks. I've Cc-ed Pawel and
>> Marek who have a better understanding of the mm internals than I do. Hopefully
>> they can review the code.
>>
>> It definitely looks like a good idea, and if nobody else will comment on the vb2
>> patches in the next 2 weeks, then I'll try to review it myself (for whatever that's
>> worth).
> 
> I'm really sorry that I didn't manage to find time to review this 
> patchset. I really
> like the idea of moving pfn lookup from videobuf2/driver to some common 
> code in mm
> and it is really great that someone managed to provide nice generic code 
> for it.
> 
> I've applied the whole patchset onto v4.0 and tested it on Odroid U3 
> (with some
> additional patches). VideoBuf2-dc works still fine with USERPTR gathered 
> from other's
> device mmaped buffer. You can add my:
> 
> Acked-by: Marek Szyprowski <m.szyprowski@samsung.com>
> Tested-by: Marek Szyprowski <m.szyprowski@samsung.com>

Thanks!

> 
> for the patches 1-8. Patch 9/9 doesn't apply anymore, so I've skipped 
> it. Patch 2
> needs a small fixup - you need to add '#include <linux/vmalloc.h>', 
> because otherwise
> it doesn't compile. There have been also a minor conflict to be resolved 
> in patch 7.

I've just added patch 1/9 to my pull request for 4.2. But for patch 2/9 I need
Acks from the mm maintainers. I think it makes sense if patches 2-8 all go
in together via the linux-media tree. Jan, can you reach out to the right
devs to get Acks?

Regards,

	Hans

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-04-24 11:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 11:56 Jan Kara
2015-03-17 11:56 ` [PATCH 1/9] [media] vb2: Push mmap_sem down to memops Jan Kara
2015-03-17 11:56 ` [PATCH 2/9] mm: Provide new get_vaddr_pfns() helper Jan Kara
2015-04-30 15:55   ` Mel Gorman
2015-05-04 15:14     ` Jan Kara
2015-03-17 11:56 ` [PATCH 3/9] media: omap_vout: Convert omap_vout_uservirt_to_phys() to use get_vaddr_pfns() Jan Kara
2015-03-17 11:56 ` [PATCH 4/9] vb2: Provide helpers for mapping virtual addresses Jan Kara
2015-03-17 11:56 ` [PATCH 5/9] media: vb2: Convert vb2_dma_sg_get_userptr() to use pinned pfns Jan Kara
2015-03-17 11:56 ` [PATCH 6/9] media: vb2: Convert vb2_vmalloc_get_userptr() to use pfns vector Jan Kara
2015-03-17 11:56 ` [PATCH 7/9] media: vb2: Convert vb2_dc_get_userptr() " Jan Kara
2015-03-17 11:56 ` [PATCH 8/9] media: vb2: Remove unused functions Jan Kara
2015-03-17 11:56 ` [PATCH 9/9] drm/exynos: Convert g2d_userptr_get_dma_addr() to use get_vaddr_pfn() Jan Kara
2015-04-02 15:02 ` [PATCH 0/9 v2] Helper to abstract vma handling in media layer Jan Kara
2015-04-02 15:25   ` Hans Verkuil
2015-04-24 10:59     ` Marek Szyprowski
2015-04-24 11:07       ` Hans Verkuil [this message]
2015-04-24 16:08         ` Jan Kara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=553A23F9.1080504@xs4all.nl \
    --to=hverkuil@xs4all.nl \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=jack@suse.cz \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=mchehab@osg.samsung.com \
    --cc=pawel@osciak.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox