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
| ||
|
Date: Fri, 29 Mar 2013 07:31:01 -0400 From: Peter Hurley <peter@...leysoftware.com> To: Clemens Ladisch <clemens@...isch.de> Cc: Stefan Richter <stefanr@...6.in-berlin.de>, linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org Subject: Re: [PATCH] firewire: Enable physical DMA above 4GB On Fri, 2013-03-29 at 12:19 +0100, Clemens Ladisch wrote: > Peter Hurley wrote: > > On Fri, 2013-03-29 at 11:44 +0100, Stefan Richter wrote: > >>> On Mar 26 Peter Hurley wrote: > >>>> The FW643e-2 is natively PCIe (not behind a bridge) and supports phys > >>>> DMA past 4GB (the datasheet says all 48 bits but I can only test it out > >>>> to 10GB). > >>>> > >>>> I thought the FW643e was as well? You'll have to test that out :) > >> > >> Does lspci or something similar show which PCI devices are capable of 64 bit > >> wide addressing? > > > > Not definitively. > > > > Usually (but not always), if the host registers are 64-bit addressable, > > then the device supports DAC. > > DACs are a feature of conventional PCI. > > All PCI Express devices are 64-bit addressable. In the lspci output, PCIe > devices have the "Express" capability. The "device" could be sitting behind a PCIe-PCI bridge that _only_ supports the host window for 64-bit. All other 64-bit decodes could return garbage. > However, whether a device can *generate* 64-bit DMA requests is completely > device-specific. -- 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/
Powered by blists - more mailing lists