From: Jiewen Yao <jiewen.yao@intel.com>
To: edk2-devel@lists.01.org
Subject: [PATCH 0/3] Add flexible exception device reporting
Date: Fri, 25 Aug 2017 15:40:43 +0800 [thread overview]
Message-ID: <1503646846-1036-1-git-send-email-jiewen.yao@intel.com> (raw)
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
next reply other threads:[~2017-08-25 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 7:40 Jiewen Yao [this message]
2017-08-25 7:40 ` [PATCH 1/3] IntelSiliconPkg/header: update PlatformVtdPolicy Jiewen Yao
2017-08-25 7:40 ` [PATCH 2/3] IntelSiliconPkg/IntelVTd: " Jiewen Yao
2017-08-25 7:40 ` [PATCH 3/3] IntelSiliconPkg/PlatformVTdSample: update ExceptionDevice Jiewen Yao
2017-08-25 9:39 ` Zeng, Star
2017-08-25 13:34 ` Yao, Jiewen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1503646846-1036-1-git-send-email-jiewen.yao@intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox