From: Usama Arif <usama.arif@linux.dev>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Vasant Hegde <vasant.hegde@amd.com>,
iommu@lists.linux.dev, joro@8bytes.org, will@kernel.org,
robin.murphy@arm.com, suravee.suthikulpanit@amd.com,
bp@alien8.de, Joerg Roedel <joerg.roedel@amd.com>,
samuelcrossley@gmail.com
Subject: Re: [PATCH 0/2] iommu/amd: Use MAX buffer size when SNP is enabled on Family 0x19
Date: Thu, 13 Aug 2026 15:17:38 +0100 [thread overview]
Message-ID: <129a38d6-3b00-4f53-9190-a0e615b3798d@linux.dev> (raw)
In-Reply-To: <20260813133503.GL662699@ziepe.ca>
On 13/08/2026 14:35, Jason Gunthorpe wrote:
> On Thu, Aug 13, 2026 at 06:18:30AM -0700, Usama Arif wrote:
>> On Mon, 20 Apr 2026 08:42:02 +0000 Vasant Hegde <vasant.hegde@amd.com> wrote:
>>
>>> 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)
>>>
>>
>> Hi,
>>
>> This series seems to break kexec in our production on Milan hosts with SEV enabled.
>> This is on the 6.18.43 stable kernel backport.
>>
>> If on top of 6.18.43 release, we revert the 2 commits, i.e.
>> Revert "iommu/amd: Use maximum PPR log buffer size when SNP is enabled on Family 0x19"
>> Revert "iommu/amd: Use maximum Event log buffer size when SNP is enabled on Family 0x19"
>>
>> kexec starts working again.
>
> This sounds like the same issue Nicolin is facing on SMMUv3, these
> larger allocations OOM the kexec kernel
>
> Jason
Thanks Jason!
Was there any solution for this issue. Could you point to a lore link for this?
next prev parent reply other threads:[~2026-08-13 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 8:42 [PATCH 0/2] iommu/amd: Use MAX buffer size when SNP is enabled on Family 0x19 Vasant Hegde
2026-04-20 8:42 ` [PATCH 1/2] iommu/amd: Use maximum Event log " 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 [this message]
2026-08-13 13:58 ` Vasant Hegde
2026-08-13 14:17 ` Usama Arif
2026-08-17 16:06 ` Usama Arif
2026-08-18 6:45 ` Vasant Hegde
2026-08-18 14:29 ` Tom Lendacky
2026-08-26 11:30 ` Vasant Hegde
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=129a38d6-3b00-4f53-9190-a0e615b3798d@linux.dev \
--to=usama.arif@linux.dev \
--cc=bp@alien8.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joerg.roedel@amd.com \
--cc=joro@8bytes.org \
--cc=robin.murphy@arm.com \
--cc=samuelcrossley@gmail.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