From: Lu Baolu <baolu.lu@linux.intel.com>
To: iommu@lists.linux-foundation.org
Cc: Yian Chen <yian.chen@intel.com>, Joerg Roedel <joro@8bytes.org>,
Ashok Raj <ashok.raj@intel.com>,
linux-kernel@vger.kernel.org, Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH 0/3] iommu/vt-d: Add support for ACPI/SATC table
Date: Tue, 2 Feb 2021 12:40:54 +0800 [thread overview]
Message-ID: <20210202044057.615277-1-baolu.lu@linux.intel.com> (raw)
Intel platform VT-d (v3.2) comes with a new type of DMAR subtable
SATC. The SATC table includes a list of SoC integrated devices
that require SATC. OS software can use this table to enable ATS
only for the devices in the list.
Yian Chen (3):
iommu/vt-d: Add new enum value and structure for SATC
iommu/vt-d: Parse SATC reporting structure
iommu/vt-d: Apply SATC policy
drivers/iommu/intel/dmar.c | 9 ++
drivers/iommu/intel/iommu.c | 161 +++++++++++++++++++++++++++++++++++-
include/acpi/actbl1.h | 11 ++-
include/linux/dmar.h | 2 +
4 files changed, 178 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2021-02-02 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 4:40 Lu Baolu [this message]
2021-02-02 4:40 ` [PATCH 1/3] iommu/vt-d: Add new enum value and structure for SATC Lu Baolu
2021-02-02 13:51 ` Joerg Roedel
2021-02-03 0:11 ` Lu Baolu
2021-02-02 16:02 ` Raj, Ashok
2021-02-03 0:15 ` Lu Baolu
2021-02-02 4:40 ` [PATCH 2/3] iommu/vt-d: Parse SATC reporting structure Lu Baolu
2021-02-02 13:53 ` Joerg Roedel
2021-02-03 0:26 ` Lu Baolu
2021-02-02 16:41 ` Raj, Ashok
2021-02-03 0:29 ` Lu Baolu
2021-02-02 4:40 ` [PATCH 3/3] iommu/vt-d: Apply SATC policy Lu Baolu
2021-02-02 13:55 ` Joerg Roedel
2021-02-03 0:33 ` Lu Baolu
2021-02-03 8:41 ` [PATCH 0/3] iommu/vt-d: Add support for ACPI/SATC table Christoph Hellwig
2021-02-03 9:29 ` Lu Baolu
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=20210202044057.615277-1-baolu.lu@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yian.chen@intel.com \
/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