linux-kernel - Re: Does pci_map_single magicly work on > 32 bit address for 32bit capable device?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1261424915.4328.6.camel@maxim-laptop>
Date:	Mon, 21 Dec 2009 21:48:35 +0200
From:	Maxim Levitsky <maximlevitsky@...il.com>
To:	Robert Hancock <hancockrwd@...il.com>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Does pci_map_single magicly work on > 32 bit address for 32bit
  capable device?

On Fri, 2009-12-11 at 18:38 -0600, Robert Hancock wrote: 
> On Fri, Dec 11, 2009 at 6:18 PM, Maxim Levitsky <maximlevitsky@...il.com> wrote:
> >> 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.
> 
> It does. See the swiotlb code. You should see some message on bootup like:
> 
> PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
> Placing 64MB software IO TLB between ffff880020000000 - ffff880024000000
> software IO TLB at phys 0x20000000 - 0x24000000

Finally got my hands on this.
I thought that swiotlb is a hardware feature and its only supported on
AMD cpus.
I think I have seen that in Kconfig

swiotlb is not used on my system, but that is just due to the fact my
system has 64 bit kernel and 2 GB of memory.

Since swiotlb is generic, this I guess means that any physical address
and aligned address can be thrown at dma api, and it will still work.
Very nice.

Although, the fact that swiotlb memory space is constant, is a bit of a
problem, because this introduces a point of failure.

For me it doesn't matter at all, because all I need is 512 bytes.

Best regards,
Maxim Levitsky

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