mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ankit Soni <Ankit.Soni@amd.com>
To: <iommu@lists.linux.dev>
Cc: <vasant.hegde@amd.com>, <suravee.suthikulpanit@amd.com>,
	<joro@8bytes.org>, <will@kernel.org>, <robin.murphy@arm.com>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] iommu/amd: Honor IVINFO[PAsize] for paging domains
Date: Mon, 19 Oct 2026 13:08:00 +0000	[thread overview]
Message-ID: <cover.1792156095.git.Ankit.Soni@amd.com> (raw)

The AMD IOMMU driver hardcodes a 52-bit output address size when it
creates paging domains. This series honors the PAsize reported in ACPI
IVRS IVinfo instead, so maps cannot exceed what firmware or a VM
advertises. Patch 1 moves page-table setup into init_pgtable_params()
after the IVHD walk, with no functional change intended. Patch 2 uses that
helper for PAsize and applies it to paging domains.

Ankit Soni (2):
  iommu/amd: Move page-table setup into init_pgtable_params()
  iommu/amd: Adhere to IVINFO[PAsize] for output address limits

 drivers/iommu/amd/amd_iommu.h       |  1 +
 drivers/iommu/amd/amd_iommu_types.h |  1 +
 drivers/iommu/amd/init.c            | 95 ++++++++++++++++-------------
 drivers/iommu/amd/iommu.c           |  4 +-
 4 files changed, 58 insertions(+), 43 deletions(-)


base-commit: 90201351a862182bdabfc1ad1c97b1e1b6ed5931
-- 
2.43.0


             reply	other threads:[~2026-10-19 13:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 13:08 Ankit Soni [this message]
2026-10-19 13:08 ` [PATCH 1/2] iommu/amd: Move page-table setup into init_pgtable_params() Ankit Soni
2026-10-19 13:08 ` [PATCH 2/2] iommu/amd: Adhere to IVINFO[PAsize] for output address limits Ankit Soni

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=cover.1792156095.git.Ankit.Soni@amd.com \
    --to=ankit.soni@amd.com \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=vasant.hegde@amd.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®