From: Vasant Hegde <vasant.hegde@amd.com>
To: Wei Wang <wei.w.wang@hotmail.com>,
jgg@nvidia.com, kevin.tian@intel.com, alex@shazbot.org,
joro@8bytes.org, thomas.lendacky@amd.com,
suravee.suthikulpanit@amd.com, aik@amd.com
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] iommupt: Do not set C-bit on MMIO backed PTEs
Date: Mon, 19 Jan 2026 12:01:06 +0530 [thread overview]
Message-ID: <e809b1dd-c03d-4f5f-998b-75b0966a37ee@amd.com> (raw)
In-Reply-To: <SI2PR01MB4393563CD72EE92D40EC565EDC88A@SI2PR01MB4393.apcprd01.prod.exchangelabs.com>
On 1/26/2026 12:49 AM, Wei Wang wrote:
> AMD Secure Memory Encryption (SME) marks individual memory pages as
> encrypted by setting the C-bit in page table entries. According to the
> AMD APM,any pages corresponding to MMIO addresses must be configured
> with the C-bit clear.
>
> The current *_iommu_set_prot() implementation sets the C-bit on all PTEs
> in the IOMMU page tables. This is incorrect for PTEs backed by MMIO, and
> can break PCIe peer-to-peer communication when IOVA is used. Fix this by
> avoiding the C-bit for MMIO-backed mappings.
>
> For amdv2 IOMMU page tables, there is a usage scenario for GVA->GPA
> mappings, and for the trusted MMIO in the TEE-IO case, the C-bit will need
> to be added to GPA. However, SNP guests do not yet support vIOMMU, and the
> trusted MMIO support is not ready in upstream. Adding the C-bit for trusted
> MMIO can be considered once those features land.
>
> Fixes: 879ced2bab1b ("iommupt: Add the AMD IOMMU v1 page table format")
> Fixes: aef5de756ea8 ("iommupt: Add the x86 64 bit page table format")
> Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Wei Wang <wei.w.wang@hotmail.com>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
> Reviewed-by: Kevin Tian <kevin.tian@intel.com>
Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>
-Vasant
next prev parent reply other threads:[~2026-01-19 6:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 19:19 [PATCH v5 0/2] iommu: Avoid setting C-bit for MMIO addresses Wei Wang
2026-01-19 9:20 ` Jörg Rödel
2026-01-25 19:19 ` [PATCH v5 1/2] iommupt: Do not set C-bit on MMIO backed PTEs Wei Wang
2026-01-19 6:31 ` Vasant Hegde [this message]
2026-01-25 19:19 ` [PATCH v5 2/2] vfio/type1: Set IOMMU_MMIO in dma->prot for MMIO-backed addresses Wei Wang
2026-02-04 15:16 ` Wei Wang
2026-02-25 8:45 ` Wei Wang
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=e809b1dd-c03d-4f5f-998b-75b0966a37ee@amd.com \
--to=vasant.hegde@amd.com \
--cc=aik@amd.com \
--cc=alex@shazbot.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=thomas.lendacky@amd.com \
--cc=wei.w.wang@hotmail.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
all inboxes | Powered by JetHome®