[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <85v7o1v4ya.fsf@amd.com>
Date: Wed, 9 Jul 2025 14:01:17 +0000
From: Nikunj A Dadhania <nikunj@....com>
To: Ard Biesheuvel <ardb+git@...gle.com>, <linux-kernel@...r.kernel.org>
CC: <linux-efi@...r.kernel.org>, <x86@...nel.org>, Ard Biesheuvel
<ardb@...nel.org>, Borislav Petkov <bp@...en8.de>, Ingo Molnar
<mingo@...nel.org>, Dionna Amalie Glaze <dionnaglaze@...gle.com>, "Kevin
Loughlin" <kevinloughlin@...gle.com>, Tom Lendacky <thomas.lendacky@....com>,
Josh Poimboeuf <jpoimboe@...nel.org>, Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH v4 00/24] x86: strict separation of startup code
Ard Biesheuvel <ardb+git@...gle.com> writes:
> From: Ard Biesheuvel <ardb@...nel.org>
>
> Build tested defconfig and allmodconfig
>
> !!! Boot tested on non-SEV guest ONLY !!!!
>
> Again, I will need to lean on Tom to determine whether this breaks
> SEV-SNP guest boot. As I mentioned before, I am still waiting for
> SEV-SNP capable hardware to be delivered.
This series breaks SEV-SNP guest boot, bisect points to patch 12/24
"x86/sev: Unify SEV-SNP hypervisor feature check". If I revert this
patch SEV-SNP guest boot fine. I will continue debugging it further.
Regards,
Nikunj
Powered by blists - more mailing lists