Re: Does pci_map_single magicly work on > 32 bit address for 32bitcapable device?

[Maxim Levitsky]

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





--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/