From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Borislav Petkov <bp@alien8.de>,
Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: x86/amd late microcode thread loading slows down boot
Date: Thu, 14 Nov 2024 12:03:41 +0000 [thread overview]
Message-ID: <3f6a84bd-af4a-4ffa-8205-25b2c9084893@citrix.com> (raw)
In-Reply-To: <20241114095639.GDZzXJV1EDJlMqv24c@fat_crate.local>
On 14/11/2024 9:56 am, Borislav Petkov wrote:
> On Thu, Nov 07, 2024 at 09:58:12PM +0100, Thomas De Schampheleire wrote:
>> Boris, perhaps you can propose a more fine-tuned flushing? I'd be happy to try
>> that.
> Let's see if that does the deal too.
>
> Thx.
>
> ---
> diff --git a/arch/x86/include/asm/tlb.h b/arch/x86/include/asm/tlb.h
> index 580636cdc257..4d3c9d00d6b6 100644
> --- a/arch/x86/include/asm/tlb.h
> +++ b/arch/x86/include/asm/tlb.h
> @@ -34,4 +34,8 @@ static inline void __tlb_remove_table(void *table)
> free_page_and_swap_cache(table);
> }
>
> +static inline void invlpg(unsigned long addr)
> +{
> + asm volatile("invlpg (%0)" ::"r" (addr) : "memory");
"invlpg %0" :: "m" (*(char *)addr) : "memory"
The compiler can usually do a better job than forcing it into a plain
register.
> +}
> #endif /* _ASM_X86_TLB_H */
> diff --git a/arch/x86/kernel/cpu/microcode/amd.c b/arch/x86/kernel/cpu/microcode/amd.c
> index 31a73715d755..6a73f775ce4c 100644
> --- a/arch/x86/kernel/cpu/microcode/amd.c
> +++ b/arch/x86/kernel/cpu/microcode/amd.c
> @@ -34,6 +34,7 @@
> #include <asm/setup.h>
> #include <asm/cpu.h>
> #include <asm/msr.h>
> +#include <asm/tlb.h>
>
> #include "internal.h"
>
> @@ -489,6 +490,9 @@ static int __apply_microcode_amd(struct microcode_amd *mc)
>
> native_wrmsrl(MSR_AMD64_PATCH_LOADER, (u64)(long)&mc->hdr.data_code);
>
> + if (x86_family(bsp_cpuid_1_eax) == 0x17)
> + invlpg((u64)(long)&mc->hdr.data_code);
Ok, so it's Fam17h specific. That's good to know. Any formal statement
on the matter from AMD ?
However, these blobs are 3200 bytes long and come with a good chance of
crossing a page boundary. If you're invlpg'ing, you need to issue a
second one for the final byte of the image too.
~Andrew
next prev parent reply other threads:[~2024-11-14 12:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 17:20 Thomas De Schampheleire
2024-11-06 18:50 ` Andrew Cooper
2024-11-07 15:30 ` Borislav Petkov
2024-11-07 20:58 ` Thomas De Schampheleire
2024-11-14 9:56 ` Borislav Petkov
2024-11-14 12:03 ` Andrew Cooper [this message]
2024-11-15 20:51 ` Borislav Petkov
2024-11-16 19:32 ` Andrew Cooper
2024-11-17 18:23 ` David Laight
2024-11-17 19:52 ` Borislav Petkov
2024-11-18 15:13 ` Thomas De Schampheleire
2024-11-18 15:28 ` Borislav Petkov
2024-11-18 15:58 ` Thomas De Schampheleire
2024-11-19 10:46 ` Thomas De Schampheleire
2024-11-19 11:17 ` Borislav Petkov
2024-11-18 19:16 ` Borislav Petkov
2024-11-14 20:01 ` Thomas De Schampheleire
2024-11-19 11:21 ` [PATCH 1/2] x86/mm: Carve out INVLPG inline asm for use by others Borislav Petkov
2024-11-19 11:21 ` [PATCH 2/2] x86/microcode/AMD: Flush patch buffer mapping after application Borislav Petkov
2024-11-25 11:04 ` [tip: x86/urgent] " tip-bot2 for Borislav Petkov (AMD)
2024-11-25 11:04 ` [tip: x86/urgent] x86/mm: Carve out INVLPG inline asm for use by others tip-bot2 for Borislav Petkov (AMD)
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=3f6a84bd-af4a-4ffa-8205-25b2c9084893@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.de_schampheleire@nokia.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 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®