From: Vasant Hegde <vasant.hegde@amd.com>
To: <iommu@lists.linux.dev>, <joro@8bytes.org>
Cc: <will@kernel.org>, <robin.murphy@arm.com>,
<suravee.suthikulpanit@amd.com>, <bp@alien8.de>,
Vasant Hegde <vasant.hegde@amd.com>,
Joerg Roedel <joerg.roedel@amd.com>
Subject: [PATCH 0/2] iommu/amd: Use MAX buffer size when SNP is enabled on Family 0x19
Date: Mon, 20 Apr 2026 08:42:02 +0000 [thread overview]
Message-ID: <20260420084204.12263-1-vasant.hegde@amd.com> (raw)
This series addresses CVE-2023-20585 [1] by increasing the AMD IOMMU
Event log and PPR log buffer sizes to the maximum supported value (512K)
on affected CPU families when SNP is enabled.
Use MAX buffer size when SNP is enabled on Milan/Genoa. Impacted buffers:
- Milan : Event log (PPR/GALog is not supported when SNP is enabled)
- Genoa : Event and PPR log (GALog is not supported when SNP is enabled)
[1] https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3016.html
Cc: Borislav Petkov <bp@alien8.de>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>
Vasant Hegde (2):
iommu/amd: Use maximum Event log buffer size when SNP is enabled on Family 0x19
iommu/amd: Use maximum PPR log buffer size when SNP is enabled on Family 0x19
drivers/iommu/amd/amd_iommu.h | 3 +
drivers/iommu/amd/amd_iommu_types.h | 21 +++--
drivers/iommu/amd/init.c | 123 ++++++++++++++++++++--------
drivers/iommu/amd/iommu.c | 2 +-
drivers/iommu/amd/ppr.c | 8 +-
5 files changed, 110 insertions(+), 47 deletions(-)
--
2.31.1
next reply other threads:[~2026-04-20 8:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 8:42 Vasant Hegde [this message]
2026-04-20 8:42 ` [PATCH 1/2] iommu/amd: Use maximum Event log buffer size when SNP is enabled on Family 0x19 Vasant Hegde
2026-04-20 8:42 ` [PATCH 2/2] iommu/amd: Use maximum PPR " Vasant Hegde
2026-04-23 12:57 ` [PATCH 0/2] iommu/amd: Use MAX " Srivastava, Dheeraj Kumar
2026-04-27 11:50 ` Jörg Rödel
2026-08-13 13:18 ` Usama Arif
2026-08-13 13:35 ` Jason Gunthorpe
2026-08-13 14:17 ` Usama Arif
2026-08-13 13:58 ` Vasant Hegde
2026-08-13 14:17 ` Usama Arif
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=20260420084204.12263-1-vasant.hegde@amd.com \
--to=vasant.hegde@amd.com \
--cc=bp@alien8.de \
--cc=iommu@lists.linux.dev \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.