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>
prev parent reply other threads:[~2018-11-28 15:21 UTC|newest]
Thread overview: 18+ 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 18:13 ` Randy Dunlap
2018-11-16 5:30 ` Souptick Joarder
2018-11-16 6:40 ` Matthew Wilcox
2018-11-16 8:15 ` Souptick Joarder
2018-11-16 16:59 ` Randy Dunlap
2018-11-16 17:48 ` Slavomir Kaslev
2018-11-16 18:28 ` Mike Rapoport
2018-11-17 6:56 ` Souptick Joarder
2018-11-17 14:37 ` Matthew Wilcox
2018-11-19 15:13 ` Souptick Joarder
2018-11-19 16:26 ` Mike Rapoport
2018-11-19 17:45 ` Souptick Joarder
2018-11-23 7:19 ` Mike Rapoport
2018-11-21 11:19 ` William Kucharski
2018-11-21 12:35 ` Matthew Wilcox
2018-11-21 14:29 ` William Kucharski
2018-11-28 15:21 ` Heiko Stübner [this message]
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=linux-arm-kernel@lists.infradead.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).