From: Stefano Panella <stefano.panella@citrix.com>
To: <gregkh@linuxfoundation.org>, <maarten.lankhorst@canonical.com>,
<mingo@kernel.org>, <stefano.stabellini@eu.citrix.com>,
<konrad.wilk@oracle.com>, <zoltan.kiss@citrix.com>,
<joe@perches.com>
Cc: <linux-kernel@vger.kernel.org>, <xen-devel@lists.xen.org>,
Stefano Panella <stefano.panella@citrix.com>
Subject: [RFC] dma-mapping: dma_alloc_coherent_mask return dma_addr_t
Date: Tue, 10 Dec 2013 16:05:37 +0000 [thread overview]
Message-ID: <1386691537-10319-1-git-send-email-stefano.panella@citrix.com> (raw)
When running a 32bit kernel there are still some pci devices
capable of 64bit addressing (eg. sound/pci/hda/hda_intel.c)
If these drivers are setting:
dev->coherent_dma_mask = 0xFFFFFFFFFFFFFFFF
why dma_alloc_coherent_mask is returning unsigned long instead
of dma_addr_t resulting in truncation of the dma_mask to 32bit
if running a 32bit kernel?
There are some examples where the dma_alloc_coherent running
32bit kernel can return a machine address bigger than 32bit.
This can be true in particular if running the 32bit kernel as a
pv dom0 under the Xen Hypervisor or PAE on bare metal.
In both cases it would be good if dma_alloc_coherent could return
a machine address bigger than 32bit so more constrained 32bit address
space could be used by devices not 64bit capable.
I am proposing this patch to eliminate this limitation but I agree
that there might be some more reasons to do it in the current way of
which I am not awere.
This is why I am just asking for a RFC.
The current patch apply to v3.13-rc3-74-g6c843f5
Signed-off-by: Stefano Panella <stefano.panella@citrix.com>
---
Documentation/DMA-API.txt | 5 ++---
arch/x86/include/asm/dma-mapping.h | 8 ++++----
arch/x86/kernel/pci-dma.c | 2 +-
drivers/xen/swiotlb-xen.c | 6 +++---
4 files changed, 10 insertions(+), 11 deletions(-)
diff --git a/Documentation/DMA-API.txt b/Documentation/DMA-API.txt
index e865279..483458b 100644
--- a/Documentation/DMA-API.txt
+++ b/Documentation/DMA-API.txt
@@ -33,9 +33,8 @@ to make sure to flush the processor's write buffers before telling
devices to read that memory.)
This routine allocates a region of <size> bytes of consistent memory.
-It also returns a <dma_handle> which may be cast to an unsigned
-integer the same width as the bus and used as the physical address
-base of the region.
+It also returns a <dma_handle> which should be used as the physical
+address base of the region.
Returns: a pointer to the allocated region (in the processor's virtual
address space) or NULL if the allocation failed.
diff --git a/arch/x86/include/asm/dma-mapping.h b/arch/x86/include/asm/dma-mapping.h
index 808dae6..6357810 100644
--- a/arch/x86/include/asm/dma-mapping.h
+++ b/arch/x86/include/asm/dma-mapping.h
@@ -100,10 +100,10 @@ dma_cache_sync(struct device *dev, void *vaddr, size_t size,
flush_write_buffers();
}
-static inline unsigned long dma_alloc_coherent_mask(struct device *dev,
- gfp_t gfp)
+static inline dma_addr_t dma_alloc_coherent_mask(struct device *dev,
+ gfp_t gfp)
{
- unsigned long dma_mask = 0;
+ dma_addr_t dma_mask = 0;
dma_mask = dev->coherent_dma_mask;
if (!dma_mask)
@@ -114,7 +114,7 @@ static inline unsigned long dma_alloc_coherent_mask(struct device *dev,
static inline gfp_t dma_alloc_coherent_gfp_flags(struct device *dev, gfp_t gfp)
{
- unsigned long dma_mask = dma_alloc_coherent_mask(dev, gfp);
+ dma_addr_t dma_mask = dma_alloc_coherent_mask(dev, gfp);
if (dma_mask <= DMA_BIT_MASK(24))
gfp |= GFP_DMA;
diff --git a/arch/x86/kernel/pci-dma.c b/arch/x86/kernel/pci-dma.c
index 872079a..a061f7b 100644
--- a/arch/x86/kernel/pci-dma.c
+++ b/arch/x86/kernel/pci-dma.c
@@ -90,7 +90,7 @@ void *dma_generic_alloc_coherent(struct device *dev, size_t size,
dma_addr_t *dma_addr, gfp_t flag,
struct dma_attrs *attrs)
{
- unsigned long dma_mask;
+ dma_addr_t dma_mask;
struct page *page;
unsigned int count = PAGE_ALIGN(size) >> PAGE_SHIFT;
dma_addr_t addr;
diff --git a/drivers/xen/swiotlb-xen.c b/drivers/xen/swiotlb-xen.c
index 1eac073..6f75599 100644
--- a/drivers/xen/swiotlb-xen.c
+++ b/drivers/xen/swiotlb-xen.c
@@ -54,10 +54,10 @@
*/
#ifndef CONFIG_X86
-static unsigned long dma_alloc_coherent_mask(struct device *dev,
- gfp_t gfp)
+static dma_addr_t dma_alloc_coherent_mask(struct device *dev,
+ gfp_t gfp)
{
- unsigned long dma_mask = 0;
+ dma_addr_t dma_mask = 0;
dma_mask = dev->coherent_dma_mask;
if (!dma_mask)
--
1.7.9.5
next reply other threads:[~2013-12-10 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 16:05 Stefano Panella [this message]
2013-12-17 17:57 ` Konrad Rzeszutek Wilk
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=1386691537-10319-1-git-send-email-stefano.panella@citrix.com \
--to=stefano.panella@citrix.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=mingo@kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.org \
--cc=zoltan.kiss@citrix.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®