From: "Aithal, Srikanth" <sraithal@amd.com>
To: Ard Biesheuvel <ardb@kernel.org>,
Sean Christopherson <seanjc@google.com>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
KVM <kvm@vger.kernel.org>, Ashish Kalra <Ashish.Kalra@amd.com>,
Borislav Petkov <bp@alien8.de>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: AMD SNP guest kdump broken since linuxnext-20250908
Date: Wed, 24 Sep 2025 20:13:35 +0530 [thread overview]
Message-ID: <616d8f02-a4ea-4f9a-ad4f-8bcbc2ccc887@amd.com> (raw)
In-Reply-To: <CAMj1kXHxUVowtCqBCKRE2_dv4TSUK6Kgwd46RzjjskAW8qYjHg@mail.gmail.com>
On 9/24/2025 7:45 PM, Ard Biesheuvel wrote:
> Hi,
>
> On Wed, 24 Sept 2025 at 15:25, Sean Christopherson <seanjc@google.com> wrote:
>>
>> +Ard and Boris (and Tom for good measure)
>>
>
> Thanks for the cc, and apologies for the breakage.
>
> Does this help?
>
> --- a/arch/x86/boot/startup/sev-startup.c
> +++ b/arch/x86/boot/startup/sev-startup.c
> @@ -44,7 +44,7 @@
> /* Include code shared with pre-decompression boot stage */
> #include "sev-shared.c"
>
> -void __init
> +void
> early_set_pages_state(unsigned long vaddr, unsigned long paddr,
> unsigned long npages, const struct psc_desc *desc)
> {
Tested this patch on top of 6.17.0-rc7-next-20250923
[https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tag/?h=next-20250923].
This patch fixes the issue reported for the SNP guest type. It was also
tested on [normal, SEV, SEV-ES] guest types, and kdump works fine on all.
Reported-by: Srikanth Aithal <Srikanth.Aithal@amd.com>
Tested-by: Srikanth Aithal <Srikanth.Aithal@amd.com>
next prev parent reply other threads:[~2025-09-24 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 12:05 Aithal, Srikanth
2025-09-24 13:25 ` Sean Christopherson
2025-09-24 14:15 ` Ard Biesheuvel
2025-09-24 14:43 ` Aithal, Srikanth [this message]
2025-09-24 14:45 ` Borislav Petkov
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=616d8f02-a4ea-4f9a-ad4f-8bcbc2ccc887@amd.com \
--to=sraithal@amd.com \
--cc=Ashish.Kalra@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=seanjc@google.com \
--cc=thomas.lendacky@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
all inboxes | Powered by JetHome®