From: Kyung Min Park <kyung.min.park@intel.com>
To: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Cc: ravi.v.shankar@intel.com, kevin.tian@intel.com,
ashok.raj@intel.com, dwmw2@infradead.org, ricardo.neri@intel.com,
kyung.min.park@intel.com, will@kernel.org
Subject: [PATCH v3 0/3] Audit Capability and Extended Capability among IOMMUs
Date: Tue, 22 Dec 2020 16:29:01 -0800 [thread overview]
Message-ID: <20201223002904.13872-1-kyung.min.park@intel.com> (raw)
Modern platforms have more than one IOMMU. Each IOMMU has its own
feature set. Some of these features must be consistent among IOMMUs.
Otherwise, these differences can lead to improper behavior in the system.
On the other hand, for some features, each IOMMU can have different
capacity values. So, different actions are required to deal with the
inconsistencies depending on the IOMMU features.
Currently, some inconsistencies are ignored by the IOMMU driver.
This patchset checks IOMMU capabilities and extended capabilities
centralizedly during boot and take different actions according to
the impacts caused by the mismatches.
For example:
1. Disable Shared Virtual Memory.
2. Use common capacity values (normally the lowest capacity value) for
all IOMMUs.
3. Report feature mismatches.
Detailed information on the IOMMU Capability / Extended Capability can
be found in Intel VT-d Specification.
Link: https://software.intel.com/sites/default/files/managed/c5/15/vt-directed-io-spec.pdf
ChangeLog:
- Change from v2 to v3:
1. fix the wrong macro names and rebase to v5.10.
- Change from v1 to v2:
1. Add missing cap/ecaps for audit.
2. Refactor function/macros overal suggested by Lu, Baolu.
2. Skip audit for gfx dedicated IOMMU.
3. Change commit message.
Kyung Min Park (3):
iommu/vt-d: Audit IOMMU Capabilities and add helper functions
iommu/vt-d: Move capability check code to cap_audit files
iommu/vt-d: Disable SVM in the platform when IOMMUs have
inconsistencies
drivers/iommu/intel/Makefile | 2 +-
drivers/iommu/intel/cap_audit.c | 219 ++++++++++++++++++++++++++++
drivers/iommu/intel/cap_audit.h | 132 +++++++++++++++++
drivers/iommu/intel/iommu.c | 85 ++---------
drivers/iommu/intel/irq_remapping.c | 8 +
drivers/iommu/intel/svm.c | 3 +-
include/linux/intel-iommu.h | 39 ++---
7 files changed, 394 insertions(+), 94 deletions(-)
create mode 100644 drivers/iommu/intel/cap_audit.c
create mode 100644 drivers/iommu/intel/cap_audit.h
--
2.17.1
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2020-12-23 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 0:29 Kyung Min Park [this message]
2020-12-23 0:29 ` [PATCH v3 1/3] iommu/vt-d: Audit IOMMU Capabilities and add helper functions Kyung Min Park
2020-12-23 0:29 ` [PATCH v3 2/3] iommu/vt-d: Move capability check code to cap_audit files Kyung Min Park
2020-12-23 0:29 ` [PATCH v3 3/3] iommu/vt-d: Disable SVM in the platform when IOMMUs have inconsistencies Kyung Min Park
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-all 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=20201223002904.13872-1-kyung.min.park@intel.com \
--to=kyung.min.park@intel.com \
--cc=ashok.raj@intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@intel.com \
--cc=will@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).