During VTd enabling, we notice a platform may want to
add exception device based upon VendorId/DeviceId.
We update GetExceptionDeviceList() function to support both style.
1) Support Device scope based reporting:
Such as, Seg:0/StartBus:0/(Dev:1C|Func:0)/(Dev:0|Func:0)
2) Support PCI VendorId/DeviceId based reporting
Such as, VID:8086|DID:9D2F|Rev:21|SVID:8086|SDID:7270
Jiewen Yao (3):
IntelSiliconPkg/header: update PlatformVtdPolicy
IntelSiliconPkg/IntelVTd: update PlatformVtdPolicy
IntelSiliconPkg/PlatformVTdSample: update ExceptionDevice
IntelSiliconPkg/Include/Protocol/PlatformVtdPolicy.h | 51 ++++-
IntelSiliconPkg/IntelVTdDxe/DmaProtection.c | 143 ++++++++++++-
IntelSiliconPkg/IntelVTdDxe/DmaProtection.h | 119 ++++++++---
IntelSiliconPkg/IntelVTdDxe/DmarAcpiTable.c | 48 +++--
IntelSiliconPkg/IntelVTdDxe/PciInfo.c | 212 ++++++++++++--------
IntelSiliconPkg/IntelVTdDxe/TranslationTable.c | 28 +--
IntelSiliconPkg/IntelVTdDxe/TranslationTableEx.c | 20 +-
IntelSiliconPkg/IntelVTdDxe/VtdReg.c | 14 +-
IntelSiliconPkg/PlatformVTdSampleDxe/PlatformVTdSampleDxe.c | 80 +++++++-
9 files changed, 543 insertions(+), 172 deletions(-)
--
2.7.4.windows.1
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel