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: Sat, 16 Nov 2024 19:32:10 +0000 [thread overview]
Message-ID: <831eef13-5442-496b-babf-7dc3df7a8cac@citrix.com> (raw)
In-Reply-To: <20241115205114.GCZze0QtUKbeXdFEHe@fat_crate.local>
On 15/11/2024 8:51 pm, Borislav Petkov wrote:
> On Thu, Nov 14, 2024 at 12:03:41PM +0000, Andrew Cooper wrote:
>> Ok, so it's Fam17h specific. That's good to know. Any formal statement
>> on the matter from AMD ?
> You can use my commit message for now... I'm working on something more
> formal although I have no idea yet what format that should have ...
Best would be a new erratum in the revision guides.
Thanks,
~Andrew
next prev parent reply other threads:[~2024-11-16 19:32 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
2024-11-15 20:51 ` Borislav Petkov
2024-11-16 19:32 ` Andrew Cooper [this message]
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=831eef13-5442-496b-babf-7dc3df7a8cac@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®