From: Will Deacon <will@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <jroedel@suse.de>,
Jerry Snitselaar <jsnitsel@redhat.com>,
patches@lists.linux.dev, Stable@vger.kernel.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Ankit.Soni@amd.com
Subject: Re: [PATCH v2] iommu/amd: Fix geometry.aperture_end for V2 tables
Date: Thu, 17 Jul 2025 11:03:56 +0100 [thread overview]
Message-ID: <aHjKjDunWlpF_aSx@willie-the-truck> (raw)
In-Reply-To: <20250716124929.GA2138968@nvidia.com>
Hi Jason, Vasant,
On Wed, Jul 16, 2025 at 09:49:29AM -0300, Jason Gunthorpe wrote:
> On Thu, Jun 12, 2025 at 10:54:00AM +0530, Vasant Hegde wrote:
> > > Adjust dma_max_address() to remove the top VA bit. It now returns:
> > >
> > > 5 Level:
> > > Before 0x1ffffffffffffff
> > > After 0x0ffffffffffffff
> > > 4 Level:
> > > Before 0xffffffffffff
> > > After 0x7fffffffffff
> > >
> > > Fixes: 11c439a19466 ("iommu/amd/pgtbl_v2: Fix domain max address")
> > > Link: https://lore.kernel.org/all/8858d4d6-d360-4ef0-935c-bfd13ea54f42@amd.com/
> > > Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
> >
> > Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>
>
> Will, can you pick this up please? It seems to have been overlooked
Thanks, I had missed this one (I only trawled the list for the two weeks
prior to Joerg going on holiday).
I'll pick it up, but please now that the preceding:
if (pgtable == PD_MODE_V1)
part now returns:
PM_LEVEL_SIZE(amd_iommu_hpt_level);
instead of:
~0ULL;
thanks to 025d1371cc8c ("iommu/amd: Add efr[HATS] max v1 page table
level"). I'm assuming that's fine because this change is about v2, but I
just wanted to highlight it in case there's a potential issue.
Will
next prev parent reply other threads:[~2025-07-17 10:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 23:58 [PATCH v2] iommu/amd: Fix geometry.aperture_end for V2 tables Jason Gunthorpe
2025-06-10 2:53 ` Baolu Lu
2025-06-12 5:24 ` Vasant Hegde
2025-06-12 12:32 ` Jason Gunthorpe
2025-07-16 12:49 ` Jason Gunthorpe
2025-07-17 10:03 ` Will Deacon [this message]
2025-07-17 11:58 ` Jason Gunthorpe
2025-07-17 15:50 ` Vasant Hegde
2025-07-17 10:01 ` Will Deacon
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=aHjKjDunWlpF_aSx@willie-the-truck \
--to=will@kernel.org \
--cc=Ankit.Soni@amd.com \
--cc=Stable@vger.kernel.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=jroedel@suse.de \
--cc=jsnitsel@redhat.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@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