From: Lu Baolu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Will Deacon <will@kernel.org>, Yian Chen <yian.chen@intel.com>,
Ashok Raj <ashok.raj@intel.com>,
iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
Lu Baolu <baolu.lu@linux.intel.com>
Subject: [PATCH v2 0/3] iommu/vt-d: Add support for ACPI/SATC table
Date: Wed, 3 Feb 2021 17:33:25 +0800 [thread overview]
Message-ID: <20210203093329.1617808-1-baolu.lu@linux.intel.com> (raw)
The Intel VT-d specification v3.2 comes with a new ACPI SATC (SoC-
Integrated Address Translation Cache) reporting structure. The SoC
integrated device enumerated in this table has a functional
requirement to enable its ATC (Address Translation Cache) via the
ATS capability for device operation.
This patch set adds the code to parse the SATC table, enumerates the
devices in it and satisfies the ATS requirement for them. Please help
to review. I will queue it in VT-d update for v5.12 if no objection.
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 | 8 ++
drivers/iommu/intel/iommu.c | 162 +++++++++++++++++++++++++++++++++++-
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-03 9:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-03 9:33 Lu Baolu [this message]
2021-02-03 9:33 ` [PATCH v2 1/3] iommu/vt-d: Add new enum value and structure for SATC Lu Baolu
2021-02-03 9:33 ` [PATCH v2 2/3] iommu/vt-d: Parse SATC reporting structure Lu Baolu
2021-02-03 9:33 ` [PATCH v2 3/3] iommu/vt-d: Apply SATC policy Lu Baolu
2021-02-04 1:59 ` Tian, Kevin
2021-02-04 2:13 ` Lu Baolu
2021-02-03 9:48 ` [PATCH v2 0/3] iommu/vt-d: Add support for ACPI/SATC table 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=20210203093329.1617808-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=will@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