From: Mark Hounschell <markh@compro.net>
To: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: dma_alloc_coherent - cma - and IOMMU question
Date: Fri, 30 Jan 2015 08:04:46 -0500 [thread overview]
Message-ID: <54CB816E.8060700@compro.net> (raw)
Sorry for the noise. I've read everything DMA in the kernel Doc dir and
searched the web to no avail. So I thought I might get some useful info
here.
I'm currently using a 3.18.3 (x86_64) kernel on an AMD platform. I am
currently doing 8MB DMAs to and from our device using the in kernel CMA
"cma=64M@0-4G" with no problems. This device is not DAC or
scatter/gather capable so the in kernel CMA has been great and replaced
our old bigphysarea usage.
We simply use dma_alloc_coherent and pass the dma_addr_t *dma_handle
returned from the dma_alloc_coherent function to our device as the
"bus/pci" address to use.
We also use remap_pfn_range on that dma_addr_t *dma_handle returned from
the dma_alloc_coherent function to mmap userland to the buffer. All is
good until I enable the IOMMU. I then either get IO_PAGE_FAULTs, the DMA
just quietly never completes or the system gets borked.
[ 106.115725] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0
domain=0x001b address=0x00000000aa500000 flags=0x0010]
[ 106.115729] AMD-Vi: Event logged [IO_PAGE_FAULT device=03:00.0
domain=0x001b address=0x00000000aa500040 flags=0x0010]
Here are the IOMMU settings in my kernel config:
#grep IOMMU .config
# CONFIG_GART_IOMMU is not set
# CONFIG_CALGARY_IOMMU is not set
CONFIG_IOMMU_HELPER=y
CONFIG_VFIO_IOMMU_TYPE1=m
CONFIG_IOMMU_API=y
CONFIG_IOMMU_SUPPORT=y
CONFIG_AMD_IOMMU=y
# CONFIG_AMD_IOMMU_STATS is not set
CONFIG_AMD_IOMMU_V2=m
CONFIG_INTEL_IOMMU=y
CONFIG_INTEL_IOMMU_DEFAULT_ON=y
CONFIG_INTEL_IOMMU_FLOPPY_WA=y
# CONFIG_IOMMU_STRESS is not set
From reading the in kernel doc it would appear that we could in fact,
using the IOMMU and the dma_map_sg function, get rid of the CMA
requirement and our device could DMA anywhere, even above the 4GB
address space limit of our device. But before going through this larger
change to our GPL driver, I want to understand if and/or why the
dma_alloc_coherent function does not appear to set up the IOMMU for me.
Is the IOMMU only supported for "streaming" DMA type and not for
"coherent"? I read no reference to this in the kernel doc?
Any hints would be greatly appreciated. Again, sorry for the noise.
Regards
Mark
reply other threads:[~2015-01-30 13:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=54CB816E.8060700@compro.net \
--to=markh@compro.net \
--cc=linux-pci@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).