From: Tom Lendacky <thomas.lendacky@amd.com>
To: Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>, Ard Biesheuvel <ardb@kernel.org>,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH 1/5] x86/sme: Clear decrypted BSS separately
Date: Fri, 24 Jul 2026 11:41:57 -0500 [thread overview]
Message-ID: <227a7dd7-445c-4b87-b0fb-cb53b2e387eb@amd.com> (raw)
In-Reply-To: <20260724030256.232690-2-brgerst@gmail.com>
On 7/23/26 22:02, Brian Gerst wrote:
> The decrypted BSS section needs to be cleared after it is remapped as
> decrypted memory. Separate it so that the normal BSS section can be
> cleared earlier.
>
> Signed-off-by: Brian Gerst <brgerst@gmail.com>
> ---
> arch/x86/kernel/vmlinux.lds.S | 2 +-
> arch/x86/mm/mem_encrypt_amd.c | 3 +++
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
> index 2438b89a4620..e64c797e06c7 100644
> --- a/arch/x86/kernel/vmlinux.lds.S
> +++ b/arch/x86/kernel/vmlinux.lds.S
> @@ -365,9 +365,9 @@ SECTIONS
> *(.bss..page_aligned)
> . = ALIGN(PAGE_SIZE);
> *(BSS_MAIN)
> - BSS_DECRYPTED
> . = ALIGN(PAGE_SIZE);
> __bss_stop = .;
> + BSS_DECRYPTED
> }
>
> /*
> diff --git a/arch/x86/mm/mem_encrypt_amd.c b/arch/x86/mm/mem_encrypt_amd.c
> index 2f8c32173972..d39e1e29bcb9 100644
> --- a/arch/x86/mm/mem_encrypt_amd.c
> +++ b/arch/x86/mm/mem_encrypt_amd.c
> @@ -479,6 +479,9 @@ void __init sme_early_init(void)
> if (!sme_me_mask)
> return;
>
> + memset(__start_bss_decrypted, 0,
> + (unsigned long) __end_bss_decrypted - (unsigned long) __start_bss_decrypted);
> +
I think this section needs to be cleared to zero regardless of whether SME
or SEV (this section is mainly used for SEV) is active. For example KVM
clock makes use of this section even if SEV is not active. So this should
probably live in clear_bss(), no?
Thanks,
Tom
> early_pmd_flags = __sme_set(early_pmd_flags);
>
> __supported_pte_mask = __sme_set(__supported_pte_mask);
next prev parent reply other threads:[~2026-07-24 16:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 3:02 [PATCH 0/5] x86/boot: Early boot cleanups Brian Gerst
2026-07-24 3:02 ` [PATCH 1/5] x86/sme: Clear decrypted BSS separately Brian Gerst
2026-07-24 16:41 ` Tom Lendacky [this message]
2026-07-24 18:57 ` Brian Gerst
2026-07-24 3:02 ` [PATCH 2/5] x86/boot/64: Clear BSS as early as possible Brian Gerst
2026-07-24 11:04 ` Nikolay Borisov
2026-07-24 11:34 ` Brian Gerst
2026-07-24 3:02 ` [PATCH 3/5] x86/boot: Remove hardcoded boot_param constants Brian Gerst
2026-07-24 13:19 ` Nikolay Borisov
2026-07-24 18:22 ` Tom Lendacky
2026-07-24 3:02 ` [PATCH 4/5] x86/boot/64: Remove copy_bootdata() call Brian Gerst
2026-07-24 3:02 ` [PATCH 5/5] x86/boot/64: Copy boot parameters and command line earlier Brian Gerst
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=227a7dd7-445c-4b87-b0fb-cb53b2e387eb@amd.com \
--to=thomas.lendacky@amd.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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.