From: "Heiko Stübner" <heiko@sntech.de>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: mhocko@suse.com, peterz@infradead.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux1394-devel@lists.sourceforge.net,
m.szyprowski@samsung.com, sfr@canb.auug.org.au,
oleksandr_andrushchenko@epam.com, linux@armlinux.org.uk,
willy@infradead.org, airlied@linux.ie,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, treding@nvidia.com,
linux-media@vger.kernel.org, keescook@chromium.org,
pawel@osciak.com, riel@surriel.com,
iommu@lists.linux-foundation.org, rppt@linux.vnet.ibm.com,
boris.ostrovsky@oracle.com, mchehab@kernel.org,
iamjoonsoo.kim@lge.com, vbabka@suse.cz, jgross@suse.com,
xen-devel@lists.xen.org, kyungmin.park@samsung.com,
stefanr@s5r6.in-berlin.de, akpm@linux-foundation.org,
robin.murphy@arm.com, kirill.shutemov@linux.intel.com
Subject: Re: [PATCH 1/9] mm: Introduce new vm_insert_range API
Date: Wed, 28 Nov 2018 16:21:05 +0100 [thread overview]
Message-ID: <3555131.qyOKUBSTPx@diego> (raw)
In-Reply-To: <20181115154530.GA27872@jordon-HP-15-Notebook-PC>
Am Donnerstag, 15. November 2018, 16:45:30 CET schrieb Souptick Joarder:
> 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.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> Reviewed-by: Matthew Wilcox <willy@infradead.org>
Except the missing EXPORT_SYMBOL for module builds this new
API is supposed to run also within the Rockchip drm driver, so
on rk3188, rk3288, rk3328 and rk3399 with graphics
Tested-by: Heiko Stuebner <heiko@sntech.de>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] mm: Introduce new vm_insert_range API
Date: Wed, 28 Nov 2018 16:21:05 +0100 [thread overview]
Message-ID: <3555131.qyOKUBSTPx@diego> (raw)
In-Reply-To: <20181115154530.GA27872@jordon-HP-15-Notebook-PC>
Am Donnerstag, 15. November 2018, 16:45:30 CET schrieb Souptick Joarder:
> 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.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> Reviewed-by: Matthew Wilcox <willy@infradead.org>
Except the missing EXPORT_SYMBOL for module builds this new
API is supposed to run also within the Rockchip drm driver, so
on rk3188, rk3288, rk3328 and rk3399 with graphics
Tested-by: Heiko Stuebner <heiko@sntech.de>
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: akpm@linux-foundation.org, willy@infradead.org, mhocko@suse.com,
kirill.shutemov@linux.intel.com, vbabka@suse.cz,
riel@surriel.com, sfr@canb.auug.org.au, rppt@linux.vnet.ibm.com,
peterz@infradead.org, linux@armlinux.org.uk,
robin.murphy@arm.com, iamjoonsoo.kim@lge.com, treding@nvidia.com,
keescook@chromium.org, m.szyprowski@samsung.com,
stefanr@s5r6.in-berlin.de, hjc@rock-chips.com, airlied@linux.ie,
oleksandr_andrushchenko@epam.com, joro@8bytes.org,
pawel@osciak.com, kyungmin.park@samsung.com, mchehab@kernel.org,
boris.ostrovsky@oracle.com, jgross@suse.com,
linux-kernel@vger.kernel.org, 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 1/9] mm: Introduce new vm_insert_range API
Date: Wed, 28 Nov 2018 16:21:05 +0100 [thread overview]
Message-ID: <3555131.qyOKUBSTPx@diego> (raw)
In-Reply-To: <20181115154530.GA27872@jordon-HP-15-Notebook-PC>
Am Donnerstag, 15. November 2018, 16:45:30 CET schrieb Souptick Joarder:
> 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.
>
> Signed-off-by: Souptick Joarder <jrdr.linux@gmail.com>
> Reviewed-by: Matthew Wilcox <willy@infradead.org>
Except the missing EXPORT_SYMBOL for module builds this new
API is supposed to run also within the Rockchip drm driver, so
on rk3188, rk3288, rk3328 and rk3399 with graphics
Tested-by: Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2018-11-28 15:21 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 15:45 [PATCH 1/9] mm: Introduce new vm_insert_range API Souptick Joarder
2018-11-15 15:45 ` Souptick Joarder
2018-11-15 15:45 ` Souptick Joarder
2018-11-15 18:13 ` Randy Dunlap
2018-11-15 18:13 ` Randy Dunlap
2018-11-15 18:13 ` Randy Dunlap
2018-11-15 18:13 ` Randy Dunlap
[not found] ` <9655a12e-bd3d-aca2-6155-38924028eb5d-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2018-11-16 5:30 ` Souptick Joarder
2018-11-16 5:30 ` Souptick Joarder
2018-11-16 5:30 ` Souptick Joarder
2018-11-16 6:40 ` Matthew Wilcox
2018-11-16 6:40 ` Matthew Wilcox
2018-11-16 6:40 ` Matthew Wilcox
2018-11-16 6:40 ` Matthew Wilcox
[not found] ` <20181116064049.GA5320-PfSpb0PWhxZc2C7mugBRk2EX/6BAtgUQ@public.gmane.org>
2018-11-16 8:15 ` Souptick Joarder
2018-11-16 8:15 ` Souptick Joarder
2018-11-16 8:15 ` Souptick Joarder
2018-11-16 16:59 ` Randy Dunlap
2018-11-16 16:59 ` Randy Dunlap
2018-11-16 16:59 ` Randy Dunlap
2018-11-16 16:59 ` Randy Dunlap
2018-11-16 8:15 ` Souptick Joarder
2018-11-16 5:30 ` Souptick Joarder
2018-11-16 17:48 ` Slavomir Kaslev
2018-11-16 17:55 ` Slavomir Kaslev
2018-11-16 17:48 ` Slavomir Kaslev
2018-11-16 17:48 ` Slavomir Kaslev
2018-11-16 18:28 ` Mike Rapoport
2018-11-16 18:28 ` Mike Rapoport
2018-11-16 18:28 ` Mike Rapoport
2018-11-17 6:56 ` Souptick Joarder
2018-11-17 6:56 ` Souptick Joarder
2018-11-17 6:56 ` Souptick Joarder
2018-11-17 14:37 ` Matthew Wilcox
2018-11-17 14:37 ` Matthew Wilcox
2018-11-17 14:37 ` Matthew Wilcox
2018-11-17 14:37 ` Matthew Wilcox
2018-11-19 15:13 ` Souptick Joarder
2018-11-19 15:13 ` Souptick Joarder
2018-11-19 15:13 ` Souptick Joarder
2018-11-19 15:13 ` Souptick Joarder
2018-11-19 16:26 ` Mike Rapoport
[not found] ` <CAFqt6zbOWX5LUTWwoGDJsGdf+pTR6N1yTPVxyr1W3-6Fte39ww-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-11-19 16:26 ` Mike Rapoport
2018-11-19 16:26 ` Mike Rapoport
2018-11-19 16:26 ` Mike Rapoport
2018-11-19 17:45 ` Souptick Joarder
2018-11-19 17:45 ` Souptick Joarder
2018-11-19 17:45 ` Souptick Joarder
[not found] ` <CAFqt6zbhodAGQz-RCB3C-wt_Mvb9QDmQ8pFeP2EO+ba2k2OccA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-11-23 7:19 ` Mike Rapoport
2018-11-23 7:19 ` Mike Rapoport
2018-11-23 7:19 ` Mike Rapoport
2018-11-23 7:19 ` Mike Rapoport
2018-11-19 17:45 ` Souptick Joarder
2018-11-21 11:19 ` William Kucharski
2018-11-21 11:19 ` William Kucharski
2018-11-21 11:19 ` William Kucharski
2018-11-21 12:35 ` Matthew Wilcox
2018-11-21 12:35 ` Matthew Wilcox
2018-11-21 12:35 ` Matthew Wilcox
2018-11-21 12:35 ` Matthew Wilcox
2018-11-21 14:29 ` William Kucharski
2018-11-21 14:29 ` William Kucharski
[not found] ` <20181121123513.GF3065-PfSpb0PWhxZc2C7mugBRk2EX/6BAtgUQ@public.gmane.org>
2018-11-21 14:29 ` William Kucharski
2018-11-21 14:29 ` William Kucharski
2018-11-21 14:29 ` William Kucharski
2018-11-21 11:19 ` William Kucharski
2018-11-17 6:56 ` Souptick Joarder
2018-11-16 18:28 ` Mike Rapoport
2018-11-28 15:21 ` Heiko Stübner [this message]
2018-11-28 15:21 ` Heiko Stübner
2018-11-28 15:21 ` Heiko Stübner
2018-11-28 15:21 ` Heiko Stübner
-- strict thread matches above, loose matches on Subject: below --
2018-11-15 15:45 Souptick Joarder
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=3555131.qyOKUBSTPx@diego \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=boris.ostrovsky@oracle.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jgross@suse.com \
--cc=jrdr.linux@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.