From: Christoph Hellwig <hch@lst.de>
To: iommu@lists.linux-foundation.org
Cc: Russell King <linux@armlinux.org.uk>,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-xtensa@linux-xtensa.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: cleanup vmap usage in the dma-mapping layer
Date: Fri, 30 Aug 2019 08:29:20 +0200 [thread overview]
Message-ID: <20190830062924.21714-1-hch@lst.de> (raw)
Hi all,
the common DMA remapping code uses the vmalloc/vmap code to create
page table entries for DMA mappings. This series lifts the currently
arm specific VM_* flag for that into common code, and also exposes
it to userspace in procfs to better understand the mappings.
next reply other threads:[~2019-08-30 6:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 6:29 Christoph Hellwig [this message]
2019-08-30 6:29 ` [PATCH 1/4] vmalloc: lift the arm flag for coherent mappings to common code Christoph Hellwig
2019-08-30 9:29 ` Russell King - ARM Linux admin
2019-08-30 14:59 ` Christoph Hellwig
2019-08-30 6:29 ` [PATCH 2/4] dma-mapping: always use VM_DMA_COHERENT for generic DMA remap Christoph Hellwig
2019-08-30 6:29 ` [PATCH 3/4] dma-mapping: introduce a dma_common_find_pages helper Christoph Hellwig
2019-10-02 12:05 ` Geert Uytterhoeven
2019-10-02 16:45 ` Robin Murphy
2019-10-06 18:45 ` Christoph Hellwig
2019-10-07 7:35 ` Geert Uytterhoeven
2019-08-30 6:29 ` [PATCH 4/4] arm: remove wrappers for the generic dma remap helpers Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2019-06-04 6:55 cleanup vmap usage in the dma-mapping layer Christoph Hellwig
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=20190830062924.21714-1-hch@lst.de \
--to=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linux@armlinux.org.uk \
--cc=robin.murphy@arm.com \
/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).