From: Baolu Lu <baolu.lu@linux.intel.com>
To: Kevin Tian <kevin.tian@intel.com>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Ashok Raj <ashok.raj@intel.com>,
Chris Wright <chrisw@sous-sol.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Asit Mallick <asit.k.mallick@intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/9] iommu/vt-d: Support a new DMAR flag
Date: Mon, 27 Jul 2026 11:04:47 +0800 [thread overview]
Message-ID: <00e3ab5e-01c3-4106-9c1a-5dd190bcafcc@linux.intel.com> (raw)
In-Reply-To: <20260702061216.388743-1-kevin.tian@intel.com>
On 7/2/26 14:12, Kevin Tian wrote:
> VT-d spec v5.2 introduces a new DMA_REMAP_OPT_OUT flag in the DMAR
> table, adding another knob to affect whether the DMA remapping
> capability should be turned on or off.
>
> While at it, first clean up the existing on/off policy messed with
> user opts and various force_on conditions in the first 8 patches.
>
> On top of the improved framework, the last patch introduces the
> support of the new bit.
>
> Some cleanups will be done after this series:
> - Cache dmar->flags instead of reading ACPI table multiple times
> - Check intel_iommu_enabled at runtime instead of using dmar_policy
> - Clean up existing warning messages (e.g. force_on panic message
> always has the "tboot:" prefix)
>
> v2:
> - Rebase to 7.2-rc1
> - Policy-oriented renaming to avoid confusion with runtime state (Baolu)
> - Warning message/comment improvements (Baolu)
> - Always return error for unsupported force_on type
> - No need to do platform optin if tboot already forces on (old behavior)
>
> v1:
> https://lore.kernel.org/linux-iommu/20260604051540.592925-1-
> kevin.tian@intel.com/
>
> Kevin Tian (9):
> iommu/vt-d: Fix no_iommu to disable platform optin
> iommu/vt-d: Force requesting ACS when tboot is enabled
> iommu/vt-d: Remove dead code when CONFIG_INTEL_IOMMU is not set
> iommu/vt-d: Consolidate dmar policy management and force_on logic
> iommu/vt-d: Use dmar_can_force_on() for platform optin
> iommu/vt-d: Call dmar_can_force_on() for tboot optin
> iommu/vt-d: Remove the 'force_on' variable
> iommu/vt-d: Remove dmar_disabled
> iommu/vt-d: Support the new DMA_REMAP_OPT_OUT flag bit
>
> drivers/iommu/intel/dmar.c | 95 +++++++++++++++++++++++++++++++++----
> drivers/iommu/intel/iommu.c | 78 +++++++++++++++---------------
> drivers/iommu/intel/iommu.h | 64 ++++++++++++++++++++-----
> drivers/iommu/intel/svm.c | 2 +-
> include/linux/dmar.h | 1 +
> 5 files changed, 180 insertions(+), 60 deletions(-)
Patch series queued for v7.3-rc1. Thanks a lot, Kevin.
prev parent reply other threads:[~2026-07-27 3:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 6:12 Kevin Tian
2026-07-02 6:12 ` [PATCH v2 1/9] iommu/vt-d: Fix no_iommu to disable platform optin Kevin Tian
2026-07-02 6:12 ` [PATCH v2 2/9] iommu/vt-d: Force requesting ACS when tboot is enabled Kevin Tian
2026-07-02 6:50 ` Tian, Kevin
2026-07-02 6:12 ` [PATCH v2 3/9] iommu/vt-d: Remove dead code when CONFIG_INTEL_IOMMU is not set Kevin Tian
2026-07-02 6:12 ` [PATCH v2 4/9] iommu/vt-d: Consolidate dmar policy management and force_on logic Kevin Tian
2026-07-02 6:12 ` [PATCH v2 5/9] iommu/vt-d: Use dmar_can_force_on() for platform optin Kevin Tian
2026-07-02 6:12 ` [PATCH v2 6/9] iommu/vt-d: Call dmar_can_force_on() for tboot optin Kevin Tian
2026-07-02 6:12 ` [PATCH v2 7/9] iommu/vt-d: Remove the 'force_on' variable Kevin Tian
2026-07-02 6:12 ` [PATCH v2 8/9] iommu/vt-d: Remove dmar_disabled Kevin Tian
2026-07-02 6:12 ` [PATCH v2 9/9] iommu/vt-d: Support the new DMA_REMAP_OPT_OUT flag bit Kevin Tian
2026-07-27 3:04 ` Baolu Lu [this message]
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=00e3ab5e-01c3-4106-9c1a-5dd190bcafcc@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=chrisw@sous-sol.org \
--cc=iommu@lists.linux.dev \
--cc=jbarnes@virtuousgeek.org \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=robin.murphy@arm.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
all inboxes | Powered by JetHome®