From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: <gregkh@linuxfoundation.org>
Cc: David Vrabel <david.vrabel@citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>, <konrad.wilk@oracle.com>,
<linux-kernel@vger.kernel.org>, <xen-devel@lists.xensource.com>,
<torvalds@linux-foundation.org>, <vinod.koul@intel.com>,
<dmaengine@vger.kernel.org>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
<bhelgaas@google.com>, <jejb@parisc-linux.org>, <deller@gmx.de>,
<linux-parisc@vger.kernel.org>,
<iommu@lists.linux-foundation.org>, <airlied@linux.ie>,
<dri-devel@lists.freedesktop.org>, <alexander.deucher@amd.com>,
<christian.koenig@amd.com>, <linux@arm.linux.org.uk>,
<linux-mips@linux-mips.org>, <ralf@linux-mips.org>,
<linux-arm-kernel@lists.infradead.org>, <dwmw2@infradead.org>
Subject: [RFC] add a struct page* parameter to dma_map_ops.unmap_page
Date: Mon, 17 Nov 2014 14:11:51 +0000 [thread overview]
Message-ID: <alpine.DEB.2.02.1411111644490.26318@kaball.uk.xensource.com> (raw)
Hi all,
I am writing this email to ask for your advice.
On architectures where dma addresses are different from physical
addresses, it can be difficult to retrieve the physical address of a
page from its dma address.
Specifically this is the case for Xen on arm and arm64 but I think that
other architectures might have the same issue.
Knowing the physical address is necessary to be able to issue any
required cache maintenance operations when unmap_page,
sync_single_for_cpu and sync_single_for_device are called.
Adding a struct page* parameter to unmap_page, sync_single_for_cpu and
sync_single_for_device would make Linux dma handling on Xen on arm and
arm64 much easier and quicker.
I think that other drivers have similar problems, such as the Intel
IOMMU driver having to call find_iova and walking down an rbtree to get
the physical address in its implementation of unmap_page.
Callers have the struct page* in their hands already from the previous
map_page call so it shouldn't be an issue for them. A problem does
exist however: there are about 280 callers of dma_unmap_page and
pci_unmap_page. We have even more callers of the dma_sync_single_for_*
functions.
Is such a change even conceivable? How would one go about it?
I think that Xen would not be the only one to gain from it, but I would
like to have a confirmation from others: given the magnitude of the
changes involved I would actually prefer to avoid them unless multiple
drivers/archs/subsystems could really benefit from them.
Cheers,
Stefano
diff --git a/include/linux/dma-mapping.h b/include/linux/dma-mapping.h
index d5d3881..158a765 100644
--- a/include/linux/dma-mapping.h
+++ b/include/linux/dma-mapping.h
@@ -31,8 +31,9 @@ struct dma_map_ops {
unsigned long offset, size_t size,
enum dma_data_direction dir,
struct dma_attrs *attrs);
- void (*unmap_page)(struct device *dev, dma_addr_t dma_handle,
- size_t size, enum dma_data_direction dir,
+ void (*unmap_page)(struct device *dev, struct page *page,
+ dma_addr_t dma_handle, size_t size,
+ enum dma_data_direction dir,
struct dma_attrs *attrs);
int (*map_sg)(struct device *dev, struct scatterlist *sg,
int nents, enum dma_data_direction dir,
@@ -41,10 +42,10 @@ struct dma_map_ops {
struct scatterlist *sg, int nents,
enum dma_data_direction dir,
struct dma_attrs *attrs);
- void (*sync_single_for_cpu)(struct device *dev,
+ void (*sync_single_for_cpu)(struct device *dev, struct page *page,
dma_addr_t dma_handle, size_t size,
enum dma_data_direction dir);
- void (*sync_single_for_device)(struct device *dev,
+ void (*sync_single_for_device)(struct device *dev, struct page *page,
dma_addr_t dma_handle, size_t size,
enum dma_data_direction dir);
void (*sync_sg_for_cpu)(struct device *dev,
next reply other threads:[~2014-11-17 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 14:11 Stefano Stabellini [this message]
2014-11-17 14:43 ` [Xen-devel] " David Vrabel
2014-11-21 11:48 ` Stefano Stabellini
2014-11-21 20:18 ` Mitchel Humpherys
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=alpine.DEB.2.02.1411111644490.26318@kaball.uk.xensource.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=airlied@linux.ie \
--cc=alexander.deucher@amd.com \
--cc=bhelgaas@google.com \
--cc=christian.koenig@amd.com \
--cc=david.vrabel@citrix.com \
--cc=deller@gmx.de \
--cc=dmaengine@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jejb@parisc-linux.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
--cc=vinod.koul@intel.com \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®