From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Rolf Offermanns <roffermanns@sysgo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmap + dma_alloc_coherent
Date: Wed, 13 Apr 2005 12:19:37 +0100 [thread overview]
Message-ID: <20050413121937.A14087@flint.arm.linux.org.uk> (raw)
In-Reply-To: <200504131243.48694.roffermanns@sysgo.com>; from roffermanns@sysgo.com on Wed, Apr 13, 2005 at 12:43:47PM +0200
On Wed, Apr 13, 2005 at 12:43:47PM +0200, Rolf Offermanns wrote:
> I would like to mmap a kernel buffer, allocated with pci_alloc_consistent()
> for DMA, to userspace and came up with the following. Since there seem to be
> some (unresolved) issues (see below) with this and I would like to do the
> RightThing(TM), I would appreciate your comments about my stuff.
This has come up before. ARM implements dma_mmap_*() to allow this
to happen, but it never got propagated to the other architectures.
Here's the (untested) x86 version. There may be a problem with
x86 not marking the pages reserved, which is required for
remap_pfn_range() to work.
diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x '*.orig' -x '*.rej' -r orig/arch/i386/kernel/pci-dma.c linux/arch/i386/kernel/pci-dma.c
--- orig/arch/i386/kernel/pci-dma.c Mon Apr 4 22:52:57 2005
+++ linux/arch/i386/kernel/pci-dma.c Mon Apr 4 22:44:45 2005
@@ -49,7 +49,7 @@ void *dma_alloc_coherent(struct device *
ret = (void *)__get_free_pages(gfp, order);
if (ret != NULL) {
- memset(ret, 0, size);
+ memset(ret, 0, PAGE_ALIGN(size));
*dma_handle = virt_to_phys(ret);
}
return ret;
diff -up -x BitKeeper -x ChangeSet -x SCCS -x _xlk -x '*.orig' -x '*.rej' -r orig/include/asm-i386/dma-mapping.h linux/include/asm-i386/dma-mapping.h
--- orig/include/asm-i386/dma-mapping.h Mon Apr 4 22:54:41 2005
+++ linux/include/asm-i386/dma-mapping.h Mon Apr 4 22:48:11 2005
@@ -16,6 +16,23 @@ void *dma_alloc_coherent(struct device *
void dma_free_coherent(struct device *dev, size_t size,
void *vaddr, dma_addr_t dma_handle);
+static inline int
+dma_mmap_coherent(struct device *dev, struct vm_area_struct *vma,
+ void *vaddr, dma_addr_t handle, size_t size)
+{
+ unsigned long offset = vma->vm_pgoff, usize;
+
+ size = PAGE_ALIGN(size) >> PAGE_SHIFT;
+ usize = (vma->vm_end - vma->vm_start) >> PAGE_SHIFT;
+
+ if (offset >= size || usize > (size - offset))
+ return -ENXIO;
+
+ return remap_pfn_range(vma, vma->vm_start,
+ (__pa(vaddr) >> PAGE_SHIFT) + offset,
+ usize << PAGE_SHIFT, vma->vm_page_prot);
+}
+
static inline dma_addr_t
dma_map_single(struct device *dev, void *ptr, size_t size,
enum dma_data_direction direction)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-04-13 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-13 10:43 mmap + dma_alloc_coherent Rolf Offermanns
2005-04-13 11:19 ` Russell King [this message]
2005-04-13 11:51 ` Rolf Offermanns
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=20050413121937.A14087@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=roffermanns@sysgo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.