From: Souptick Joarder <jrdr.linux@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
vbabka@suse.cz, Rik van Riel <riel@surriel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
rppt@linux.vnet.ibm.com, Peter Zijlstra <peterz@infradead.org>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
robin.murphy@arm.com, iamjoonsoo.kim@lge.com, treding@nvidia.com,
Kees Cook <keescook@chromium.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
stefanr@s5r6.in-berlin.de, hjc@rock-chips.com,
Heiko Stuebner <heiko@sntech.de>,
airlied@linux.ie, oleksandr_andrushchenko@epam.com,
joro@8bytes.org, pawel@osciak.com,
Kyungmin Park <kyungmin.park@samsung.com>,
mchehab@kernel.org, Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>
Cc: linux-kernel@vger.kernel.org, Linux-MM <linux-mm@kvack.org>,
linux-arm-kernel@lists.infradead.org,
linux1394-devel@lists.sourceforge.net,
dri-devel@lists.freedesktop.org,
linux-rockchip@lists.infradead.org, xen-devel@lists.xen.org,
iommu@lists.linux-foundation.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 0/9] Use vm_insert_range
Date: Wed, 21 Nov 2018 11:54:52 +0530 [thread overview]
Message-ID: <CAFqt6zZGP5DnAQd_19xKcLezOYaLsZpPr=FGxiTb7JRjTEJ4cA@mail.gmail.com> (raw)
In-Reply-To: <20181115154314.GA27850@jordon-HP-15-Notebook-PC>
On Thu, Nov 15, 2018 at 9:09 PM Souptick Joarder <jrdr.linux@gmail.com> wrote:
>
> Previouly drivers have their own way of mapping range of
> kernel pages/memory into user vma and this was done by
> invoking vm_insert_page() within a loop.
>
> As this pattern is common across different drivers, it can
> be generalized by creating a new function and use it across
> the drivers.
>
> vm_insert_range is the new API which will be used to map a
> range of kernel memory/pages to user vma.
>
> All the applicable places are converted to use new vm_insert_range
> in this patch series.
>
> Souptick Joarder (9):
> mm: Introduce new vm_insert_range API
> arch/arm/mm/dma-mapping.c: Convert to use vm_insert_range
> drivers/firewire/core-iso.c: Convert to use vm_insert_range
> drm/rockchip/rockchip_drm_gem.c: Convert to use vm_insert_range
> drm/xen/xen_drm_front_gem.c: Convert to use vm_insert_range
> iommu/dma-iommu.c: Convert to use vm_insert_range
> videobuf2/videobuf2-dma-sg.c: Convert to use vm_insert_range
> xen/gntdev.c: Convert to use vm_insert_range
> xen/privcmd-buf.c: Convert to use vm_insert_range
Any further comment on driver changes ?
>
> arch/arm/mm/dma-mapping.c | 21 ++++++-----------
> drivers/firewire/core-iso.c | 15 ++----------
> drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 20 ++--------------
> drivers/gpu/drm/xen/xen_drm_front_gem.c | 20 +++++-----------
> drivers/iommu/dma-iommu.c | 12 ++--------
> drivers/media/common/videobuf2/videobuf2-dma-sg.c | 23 ++++++-------------
> drivers/xen/gntdev.c | 11 ++++-----
> drivers/xen/privcmd-buf.c | 8 ++-----
> include/linux/mm_types.h | 3 +++
> mm/memory.c | 28 +++++++++++++++++++++++
> mm/nommu.c | 7 ++++++
> 11 files changed, 70 insertions(+), 98 deletions(-)
>
> --
> 1.9.1
>
next prev parent reply other threads:[~2018-11-21 6:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 15:43 [PATCH 0/9] Use vm_insert_range Souptick Joarder
2018-11-21 6:24 ` Souptick Joarder [this message]
2018-11-21 19:37 ` Boris Ostrovsky
2018-11-21 19:56 ` Souptick Joarder
2018-11-21 20:04 ` Boris Ostrovsky
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='CAFqt6zZGP5DnAQd_19xKcLezOYaLsZpPr=FGxiTb7JRjTEJ4cA@mail.gmail.com' \
--to=jrdr.linux@gmail.com \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=joro@8bytes.org \
--cc=keescook@chromium.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linux@armlinux.org.uk \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=mhocko@suse.com \
--cc=oleksandr_andrushchenko@epam.com \
--cc=pawel@osciak.com \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=robin.murphy@arm.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=stefanr@s5r6.in-berlin.de \
--cc=treding@nvidia.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=xen-devel@lists.xen.org \
/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;
as well as URLs for NNTP newsgroup(s).