From: Maxim Levitsky <maximlevitsky@gmail.com>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Does pci_map_single magicly work on > 32 bit address for 32bit capable device?
Date: Sat, 12 Dec 2009 02:18:57 +0200 [thread overview]
Message-ID: <1260577137.8536.20.camel@maxim-laptop> (raw)
In-Reply-To: <4B22DEA7.8040202@gmail.com>
On Fri, 2009-12-11 at 18:07 -0600, Robert Hancock wrote:
> On 12/11/2009 03:39 PM, Maxim Levitsky wrote:
> > Hi,
> >
> > I am writing a driver, and I am faced with following problem:
> >
> > I receive a kernel pointer, and I want device to dma into that memory.
> > However, device is only capable of 32 bit dma.
> >
> > I can create a 'consistent' mapping and use memcpy from/to it, but it
> > feels like waste of performance.
> >
> >
> > According to Documentation/DMA-mapping.txt, I can tell that hw supports
> > 32 bit dma using pci_set_dma_mask, however, what will happen if I pass
> > arbitrary kernel address into pci_map_single.
> > What will happen if the address is above 32 bit?
>
> The kernel should set up an IOMMU (either hardware or software) mapping
> for that memory so that the device can access it through an address
> below 4GB. This is assuming it's a 64-bit kernel (on 32-bit, a kernel
> memory address will always be below 4GB).
What do you mean by software IOMMU?
On my system there is no IOMMU present, so only way to ensure 32 bit
address is to copy pages.
pci_map_single could copy the data for write case, and pci_unmap_single
for read case, but I now strongly doubt they do.
I am not sure at all that these functions will fail if too high address
is specified....
Also, very recently, I found that in
Documentation/DMA-API.txt, there is a statement that says that
pci_map_single fails for >32 bit memory address.
I guess I just do a memcpy...
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2009-12-12 0:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 21:39 Maxim Levitsky
2009-12-12 0:07 ` Robert Hancock
2009-12-12 0:18 ` Maxim Levitsky [this message]
2009-12-12 0:38 ` Robert Hancock
2009-12-21 19:48 ` Maxim Levitsky
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=1260577137.8536.20.camel@maxim-laptop \
--to=maximlevitsky@gmail.com \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®