[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAFqt6zavi-S9ySZJTKG9zChacSD+ZCOVyyW71B1DfjggTH=Jkg@mail.gmail.com>
Date: Thu, 22 Nov 2018 01:26:51 +0530
From: Souptick Joarder <jrdr.linux@...il.com>
To: Boris Ostrovsky <boris.ostrovsky@...cle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Matthew Wilcox <willy@...radead.org>,
Michal Hocko <mhocko@...e.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
vbabka@...e.cz, Rik van Riel <riel@...riel.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
rppt@...ux.vnet.ibm.com, Peter Zijlstra <peterz@...radead.org>,
Russell King - ARM Linux <linux@...linux.org.uk>,
robin.murphy@....com, iamjoonsoo.kim@....com, treding@...dia.com,
Kees Cook <keescook@...omium.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
stefanr@...6.in-berlin.de, hjc@...k-chips.com,
Heiko Stuebner <heiko@...ech.de>, airlied@...ux.ie,
oleksandr_andrushchenko@...m.com, joro@...tes.org,
pawel@...iak.com, Kyungmin Park <kyungmin.park@...sung.com>,
mchehab@...nel.org, Juergen Gross <jgross@...e.com>,
linux-kernel@...r.kernel.org, Linux-MM <linux-mm@...ck.org>,
linux-arm-kernel@...ts.infradead.org,
linux1394-devel@...ts.sourceforge.net,
dri-devel@...ts.freedesktop.org,
linux-rockchip@...ts.infradead.org, xen-devel@...ts.xen.org,
iommu@...ts.linux-foundation.org, linux-media@...r.kernel.org
Subject: Re: [PATCH 0/9] Use vm_insert_range
On Thu, Nov 22, 2018 at 1:08 AM Boris Ostrovsky
<boris.ostrovsky@...cle.com> wrote:
>
> On 11/21/18 1:24 AM, Souptick Joarder wrote:
> > On Thu, Nov 15, 2018 at 9:09 PM Souptick Joarder <jrdr.linux@...il.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 ?
>
> Xen drivers (the last two patches) look fine to me.
Thanks, can I considered this as Reviewed-by ?
>
> -boris
>
>
> >> 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
> >>
>
Powered by blists - more mailing lists