From: jrdr.linux@gmail.com (Souptick Joarder)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] Use vm_insert_range
Date: Thu, 15 Nov 2018 21:13:14 +0530 [thread overview]
Message-ID: <20181115154314.GA27850@jordon-HP-15-Notebook-PC> (raw)
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
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 reply other threads:[~2018-11-15 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 15:43 Souptick Joarder [this message]
2018-11-21 6:24 ` [PATCH 0/9] Use vm_insert_range Souptick Joarder
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=20181115154314.GA27850@jordon-HP-15-Notebook-PC \
--to=jrdr.linux@gmail.com \
--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