public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: 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>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH 0/9 v2] Helper to abstract vma handling in media layer
Date: Thu, 2 Apr 2015 17:02:58 +0200	[thread overview]
Message-ID: <20150402150258.GA31277@quack.suse.cz> (raw)
In-Reply-To: <1426593399-6549-1-git-send-email-jack@suse.cz>

  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?

								Honza

-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  parent reply	other threads:[~2015-04-02 15:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-17 11:56 [PATCH 0/9 v2] Helper to abstract vma handling in media layer 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 ` Jan Kara [this message]
2015-04-02 15:25   ` [PATCH 0/9 v2] Helper to abstract vma handling in media layer Hans Verkuil
2015-04-24 10:59     ` Marek Szyprowski
2015-04-24 11:07       ` Hans Verkuil
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=20150402150258.GA31277@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mchehab@osg.samsung.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