From: "Suthikulpanit, Suravee" <suravee.suthikulpanit@amd.com>
To: linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
joro@8bytes.org, vasant.hegde@amd.com
Cc: jon.grimm@amd.com, frank.gorishek@amd.com,
thomas.lendacky@amd.com, santosh.shukla@amd.com
Subject: Re: [PATCH v2 0/4] iommu/amd: IVMD handling cleanup and ivmd= boot override
Date: Mon, 20 Jul 2026 17:01:56 +0700 [thread overview]
Message-ID: <dad0efa4-1422-4178-ad57-82a6ff91db79@amd.com> (raw)
In-Reply-To: <20260424092213.16976-1-suravee.suthikulpanit@amd.com>
Hi All,
Are there any other concerns on this series?
Thanks
Suravee
On 4/24/2026 4:22 PM, Suravee Suthikulpanit wrote:
> This series refreshes how the AMD IOMMU driver models IVRS IVMD entries
> after the hardware exclusion range registers were repurposed.
>
> The first patch renames the associated MMIO offsets to reflect completion-wait
> store base/limit.
>
> The second patch drops the workaround that forced IVMD exclusion ranges to
> r/w unity mappings; the driver no longer programs exclusion range
> registers, so that the workaround is obsolete.
>
> The third patch centralizes IVMD flag definitions, renames the unity-map
> structures to ivmd_entry, stores the raw IVMD flags byte from ACPI, and
> derives IOMMU reserved regions (including exclusion as IOMMU_RESV_RESERVED)
> from those flags.
>
> The fourth patch adds an ivmd= kernel parameter so up to four per-device
> IVMD-style ranges can be supplied from the command line when the IVRS
> table is wrong or incomplete, documented in kernel-parameters.txt.
>
> Change from v1:
> (https://lore.kernel.org/linux-iommu/20260420170033.6780-1-suravee.suthikulpanit@amd.com/)
>
> * Rebase on top of patch "[PATCH] iommu/amd: Remove dead code for exclusion ranges in IVMD"
> that was submitted by Yu Zhang <zhangyu1@linux.microsoft.com>.
> (https://lore.kernel.org/all/20260331152550.479841-1-zhangyu1@linux.microsoft.com/)
>
> * Patch 1: Modified to only rename the marco.
>
> * Patch 3: Reintroduce logic to parse IVMD exclusion flag to allow
> reserve region of type IOMMU_RESV_RESERVED.
>
> * Patch 4:
> - Update the sscan function to scan start, length, flags in hex format only.
> - Fix apply_ivmd_cmdline_entries() to not free the cmd, which points to
> the early_ivmd_cmdline_map[] on failure path.
>
> Thanks,
> Suravee
>
> Suravee Suthikulpanit (4):
> iommu/amd: Drop unused global exclusion range fields and init
> iommu/amd: Do not convert IVMD exclusion range to unity range
> iommu/amd: Clean up and simplify IVMD entry handling
> iommu/amd: Introduce boot option ivmd=seg:bus:dev.fun,start,size,flags
>
> .../admin-guide/kernel-parameters.txt | 16 ++
> drivers/iommu/amd/amd_iommu_types.h | 36 ++--
> drivers/iommu/amd/init.c | 159 ++++++++++++++----
> drivers/iommu/amd/iommu.c | 27 ++-
> 4 files changed, 187 insertions(+), 51 deletions(-)
>
next prev parent reply other threads:[~2026-07-20 10:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 9:22 [PATCH v2 0/4] iommu/amd: IVMD handling cleanup and ivmd= boot override Suravee Suthikulpanit
2026-04-24 9:22 ` [PATCH v2 1/4] iommu/amd: Drop unused global exclusion range fields and init Suravee Suthikulpanit
2026-04-24 9:22 ` [PATCH v2 2/4] iommu/amd: Do not convert IVMD exclusion range to unity range Suravee Suthikulpanit
2026-05-08 7:30 ` Adrian Huang12
2026-04-24 9:22 ` [PATCH v2 3/4] iommu/amd: Clean up and simplify IVMD entry handling Suravee Suthikulpanit
2026-04-24 9:22 ` [PATCH v2 4/4] iommu/amd: Introduce boot option ivmd=seg:bus:dev.fun,start,size,flags Suravee Suthikulpanit
2026-07-20 10:01 ` Suthikulpanit, Suravee [this message]
2026-07-30 12:32 ` [PATCH v2 0/4] iommu/amd: IVMD handling cleanup and ivmd= boot override Jörg Rödel
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=dad0efa4-1422-4178-ad57-82a6ff91db79@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=frank.gorishek@amd.com \
--cc=iommu@lists.linux.dev \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=santosh.shukla@amd.com \
--cc=thomas.lendacky@amd.com \
--cc=vasant.hegde@amd.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