From: Jason Gunthorpe <jgg@nvidia.com>
To: Vasant Hegde <vasant.hegde@amd.com>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
nicolinc@nvidia.com, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, will@kernel.org, joro@8bytes.org,
kevin.tian@intel.com, jsnitsel@redhat.com, iommu@lists.linux.dev,
santosh.shukla@amd.com, sairaj.arunkodilkar@amd.com,
jon.grimm@amd.com, prashanthpra@google.com, wvw@google.com,
wnliu@google.com, gptran@google.com, kpsingh@google.com,
joao.m.martins@oracle.com, alejandro.j.jimenez@oracle.com
Subject: Re: [PATCH v4 15/16] iommu/amd: Refactor logic to program the host page table in DTE
Date: Sat, 8 Nov 2025 19:03:48 -0400 [thread overview]
Message-ID: <20251108230348.GJ1932966@nvidia.com> (raw)
In-Reply-To: <62ba61a5-d172-400e-beb5-e593297129ef@amd.com>
On Sat, Nov 08, 2025 at 10:56:38PM +0530, Vasant Hegde wrote:
> > On Tue, Oct 21, 2025 at 01:43:23AM +0000, Suravee Suthikulpanit wrote:
> >> @@ -2088,37 +2104,28 @@ static void set_dte_entry(struct amd_iommu *iommu,
> >> else
> >> domid = domain->id;
> >>
> >> /*
> >> * When SNP is enabled, we can only support TV=1 with non-zero domain ID.
> >> * This is prevented by the SNP-enable and IOMMU_DOMAIN_IDENTITY check in
> >> * do_iommu_domain_alloc().
> >> */
> >> WARN_ON(amd_iommu_snp_en && (domid == 0));
> >>
> >> + amd_iommu_make_clear_dte(dev_data, &new);
> >>
> >> + old_domid = READ_ONCE(dte->data[1]) & DTE_DOMID_MASK;
> >
> > This old_domid stuff doesn't make any sense. I think the commit that
> > added it is bonkers: 36b7200f67df ("iommu/amd: Flush old domains in kdump kernel")
> >
> > The problem is that the dom ids that are present in the re-used DTE
> > table have to be reserved from the domain id alloctor at boot.
> > > If the kdump kernel tries to create new DTEs it MUST NOT re-use any
> > IDs that are actively being using in DTEs already or you get data
> > corruption. Randomly flushing IDs is just getting lucky..
>
> Good catch. Thanks!
>
> Looks like commit 38e5f33ee359 ("iommu/amd: Reuse device table for kdump") broke
> domain ID reservation in kdump path :-( We will fix it.
I suggest just reading the whole DTE and permanently reserving any
DomIDs from the ida. Just leak them forever, that is good enough for a
kdump kernel. Then get rid of this stuff above.
> > (though how does IDENTITY on a device with a PASID installed work?)
>
> Probably set_dte_identity() should call set_dte_gcr3_table () and update
> relevant fields.
Yeah, maybe so, though it might be best if the caller can detect it
and have it call both functions instead of trying to bury it.
There is a fair number of variations here as you have
blocked/identity, RID/PASID attach and PASID detach to all consider.
It would be nice if it worked properly, identity on RID while PASID is
in use has a strong real use case.
Jason
next prev parent reply other threads:[~2025-11-08 23:03 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 1:43 [PATCH v4 00/16] iommu/amd: Introduce Nested Translation support Suravee Suthikulpanit
2025-10-21 1:43 ` [PATCH v4 01/16] iommu/amd: Rename DEV_DOMID_MASK to DTE_DOMID_MASK Suravee Suthikulpanit
2025-11-08 17:25 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 02/16] iommu/amd: Make amd_iommu_pdom_id_alloc() non-static Suravee Suthikulpanit
2025-11-08 17:24 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 03/16] iommu/amd: Make amd_iommu_pdom_id_free() non-static Suravee Suthikulpanit
2025-11-08 17:26 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 04/16] iommu/amd: Make amd_iommu_device_flush_dte() non-static Suravee Suthikulpanit
2025-11-08 17:27 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 05/16] iommu/amd: Make amd_iommu_update_dte256() non-static Suravee Suthikulpanit
2025-11-08 17:27 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 06/16] iommu/amd: Make amd_iommu_make_clear_dte() non-static inline Suravee Suthikulpanit
2025-11-08 17:27 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 07/16] iommu/amd: Make amd_iommu_completion_wait() non-static Suravee Suthikulpanit
2025-11-08 17:32 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 08/16] iommufd: Introduce data struct for AMD nested domain allocation Suravee Suthikulpanit
2025-11-08 17:30 ` Vasant Hegde
2025-10-21 1:43 ` [PATCH v4 09/16] iommu/amd: Always enable GCR3TRPMode when supported Suravee Suthikulpanit
2025-10-23 2:24 ` Nicolin Chen
2025-11-08 17:39 ` Vasant Hegde
2025-11-11 13:59 ` Suthikulpanit, Suravee
2025-10-21 1:43 ` [PATCH v4 10/16] iommu/amd: Add support for nest parent domain allocation Suravee Suthikulpanit
2025-10-23 2:27 ` Nicolin Chen
2025-10-23 20:08 ` Suthikulpanit, Suravee
2025-10-21 1:43 ` [PATCH v4 11/16] iommu/amd: Introduce struct amd_iommu_viommu Suravee Suthikulpanit
2025-10-22 20:00 ` Jason Gunthorpe
2025-10-23 2:33 ` Nicolin Chen
2025-10-21 1:43 ` [PATCH v4 12/16] iommu/amd: Add support for nested domain allocation Suravee Suthikulpanit
2025-10-22 20:01 ` Jason Gunthorpe
2025-10-21 1:43 ` [PATCH v4 13/16] iommu/amd: Track host Domain ID mapping for each guest Domain ID Suravee Suthikulpanit
2025-10-22 20:08 ` Jason Gunthorpe
2025-11-05 10:50 ` Suthikulpanit, Suravee
2025-11-05 13:35 ` Jason Gunthorpe
2025-10-21 1:43 ` [PATCH v4 14/16] iommu/amd: Refactor persistent DTE bits programming into amd_iommu_make_clear_dte() Suravee Suthikulpanit
2025-10-23 2:49 ` Nicolin Chen
2025-10-21 1:43 ` [PATCH v4 15/16] iommu/amd: Refactor logic to program the host page table in DTE Suravee Suthikulpanit
2025-10-23 13:08 ` Jason Gunthorpe
2025-11-08 17:26 ` Vasant Hegde
2025-11-08 23:03 ` Jason Gunthorpe [this message]
2025-11-12 18:40 ` Suthikulpanit, Suravee
2025-11-17 18:08 ` Jason Gunthorpe
2025-10-21 1:43 ` [PATCH v4 16/16] iommu/amd: Add support for nested domain attach/detach Suravee Suthikulpanit
2025-10-23 13:17 ` Jason Gunthorpe
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=20251108230348.GJ1932966@nvidia.com \
--to=jgg@nvidia.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=gptran@google.com \
--cc=iommu@lists.linux.dev \
--cc=joao.m.martins@oracle.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=jsnitsel@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kpsingh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=prashanthpra@google.com \
--cc=robin.murphy@arm.com \
--cc=sairaj.arunkodilkar@amd.com \
--cc=santosh.shukla@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.com \
--cc=will@kernel.org \
--cc=wnliu@google.com \
--cc=wvw@google.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