Patrick,
This seems like it would be a good SCT enhancement, at least for those systems
that have IOMMU capability.
Great suggestion.
Eugene
From: Patrick Georgi [mailto:patr...@georgi-clan.de]
Sent: Friday, July 26, 2013 1:44 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] XHCI DMA Buffer Issues
Am 25.07.2013 02:27, schrieb Tian, Feng:
The EDKII XhciDxe driver doesn't use PciIo.AllocateBuffer()/Map() to allocate
DMA buffers. It's mainly because EDKII is 1:1 mapping on Pci physical address
and Cpu logical address for IA architecture. AllocateBuffer() is enough for
current case.
Consider an UEFI implementation that locks down the system via IOMMU early on
(as I'm thinking about doing for coreboot).
Nice, isolated student project, by the way.
That would probably hook into PciIo.Map() to have the IOMMU engine whitelist
access by the specific hardware to that buffer.
A driver not mapping properly will fail in such a system and rightfully so.
Patrick
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
