From: Tom Lendacky <thomas.lendacky@amd.com>
To: Nikunj A Dadhania <nikunj@amd.com>,
linux-kernel@vger.kernel.org, bp@alien8.de
Cc: dave.hansen@linux.intel.com, tglx@kernel.org, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org
Subject: Re: [PATCH] x86/sev: Remove redundant ghcbs_initialized checks around __sev_{get,put}_ghcb()
Date: Tue, 19 May 2026 15:00:32 -0500 [thread overview]
Message-ID: <d30cea85-c454-4c43-831a-eca7d49c27db@amd.com> (raw)
In-Reply-To: <20260518102230.3394603-1-nikunj@amd.com>
On 5/18/26 05:22, Nikunj A Dadhania wrote:
> After commit 3645eb7e3915 ("x86/fred: Fix early boot failures on
> SEV-ES/SNP guests"), __sev_{get,put}_ghcb() handle the early-boot GHCB
> fallback internally, making the ghcbs_initialized guards in
> __set_pages_state() and svsm_perform_call_protocol() redundant.
>
> Remove these redundant conditionals and call __sev_{get,put}_ghcb()
> unconditionally.
>
> Also initialize state->ghcb to NULL in the early-boot path of
> __sev_get_ghcb() so that the ghcb_state is well-defined for all callers,
> even though __sev_put_ghcb() currently returns early before reading it.
>
> No functional change intended.
>
> Suggested-by: Tom Lendacky <thomas.lendacky@amd.com>
> Signed-off-by: Nikunj A Dadhania <nikunj@amd.com>
Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
> ---
> arch/x86/coco/sev/core.c | 8 ++------
> arch/x86/coco/sev/noinstr.c | 4 +++-
> arch/x86/coco/sev/svsm.c | 10 ++--------
> 3 files changed, 7 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/coco/sev/core.c b/arch/x86/coco/sev/core.c
> index 7ed3da998489d..ecd77d3217f3c 100644
> --- a/arch/x86/coco/sev/core.c
> +++ b/arch/x86/coco/sev/core.c
> @@ -367,17 +367,13 @@ static unsigned long __set_pages_state(struct snp_psc_desc *data, unsigned long
>
> local_irq_save(flags);
>
> - if (sev_cfg.ghcbs_initialized)
> - ghcb = __sev_get_ghcb(&state);
> - else
> - ghcb = boot_ghcb;
> + ghcb = __sev_get_ghcb(&state);
>
> /* Invoke the hypervisor to perform the page state changes */
> if (!ghcb || vmgexit_psc(ghcb, data))
> sev_es_terminate(SEV_TERM_SET_LINUX, GHCB_TERM_PSC);
>
> - if (sev_cfg.ghcbs_initialized)
> - __sev_put_ghcb(&state);
> + __sev_put_ghcb(&state);
>
> local_irq_restore(flags);
>
> diff --git a/arch/x86/coco/sev/noinstr.c b/arch/x86/coco/sev/noinstr.c
> index 5afd663a1c217..e1e03f12fc7bb 100644
> --- a/arch/x86/coco/sev/noinstr.c
> +++ b/arch/x86/coco/sev/noinstr.c
> @@ -121,8 +121,10 @@ noinstr struct ghcb *__sev_get_ghcb(struct ghcb_state *state)
>
> WARN_ON(!irqs_disabled());
>
> - if (!sev_cfg.ghcbs_initialized)
> + if (!sev_cfg.ghcbs_initialized) {
> + state->ghcb = NULL;
> return boot_ghcb;
> + }
>
> data = this_cpu_read(runtime_data);
> ghcb = &data->ghcb_page;
> diff --git a/arch/x86/coco/sev/svsm.c b/arch/x86/coco/sev/svsm.c
> index 2acf4a76afe7a..916d62cd17dc7 100644
> --- a/arch/x86/coco/sev/svsm.c
> +++ b/arch/x86/coco/sev/svsm.c
> @@ -74,20 +74,14 @@ int svsm_perform_call_protocol(struct svsm_call *call)
>
> flags = native_local_irq_save();
>
> - if (sev_cfg.ghcbs_initialized)
> - ghcb = __sev_get_ghcb(&state);
> - else if (boot_ghcb)
> - ghcb = boot_ghcb;
> - else
> - ghcb = NULL;
> + ghcb = __sev_get_ghcb(&state);
>
> do {
> ret = ghcb ? svsm_perform_ghcb_protocol(ghcb, call)
> : __pi_svsm_perform_msr_protocol(call);
> } while (ret == -EAGAIN);
>
> - if (sev_cfg.ghcbs_initialized)
> - __sev_put_ghcb(&state);
> + __sev_put_ghcb(&state);
>
> native_local_irq_restore(flags);
>
next prev parent reply other threads:[~2026-05-19 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-18 10:22 Nikunj A Dadhania
2026-05-19 20:00 ` Tom Lendacky [this message]
2026-05-19 21:25 ` [tip: x86/sev] " tip-bot2 for Nikunj A Dadhania
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=d30cea85-c454-4c43-831a-eca7d49c27db@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=tglx@kernel.org \
--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 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®