From: Borislav Petkov <bp@kernel.org>
To: X86 ML <x86@kernel.org>
Cc: Nikunj A Dadhania <nikunj@amd.com>,
LKML <linux-kernel@vger.kernel.org>,
"Borislav Petkov (AMD)" <bp@alien8.de>
Subject: [PATCH 0/4] x86/CPU: Fix CR4 pinning and FRED in CoCo guests
Date: Fri, 20 Mar 2026 12:54:13 +0100 [thread overview]
Message-ID: <20260320115417.4156-1-bp@kernel.org> (raw)
From: "Borislav Petkov (AMD)" <bp@alien8.de>
Hi,
the respective patches have very detailed explanations about what this is
addressing but basically, there's a window in time during boot when FRED is
not setup properly yet and if a CoCo guest generates an exception, it would
explode.
So this shuffles things a bit so that that doesn't happen.
Thx.
Borislav Petkov (AMD) (1):
x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask
Nikunj A Dadhania (2):
x86/cpu: Enable FSGSBASE early in cpu_init_exception_handling()
x86/fred: Fix early boot failures on SEV-ES/SNP guests
Peter Zijlstra (1):
x86/cpu: Add comment clarifying CRn pinning
arch/x86/coco/sev/noinstr.c | 6 ++++++
arch/x86/entry/entry_fred.c | 14 ++++++++++++++
arch/x86/kernel/cpu/common.c | 33 ++++++++++++++++++++++++++-------
3 files changed, 46 insertions(+), 7 deletions(-)
--
2.51.0
next reply other threads:[~2026-03-20 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-20 11:54 Borislav Petkov [this message]
2026-03-20 11:54 ` [PATCH 1/4] x86/cpu: Enable FSGSBASE early in cpu_init_exception_handling() Borislav Petkov
2026-03-20 11:54 ` [PATCH 2/4] x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask Borislav Petkov
2026-03-20 17:49 ` Sohil Mehta
2026-03-20 11:54 ` [PATCH 3/4] x86/fred: Fix early boot failures on SEV-ES/SNP guests Borislav Petkov
2026-03-20 11:54 ` [PATCH 4/4] x86/cpu: Add comment clarifying CRn pinning 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=20260320115417.4156-1-bp@kernel.org \
--to=bp@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nikunj@amd.com \
--cc=x86@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.