From: Borislav Petkov <bp@alien8.de>
To: "Chang S. Bae" <chang.seok.bae@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@kernel.org,
mingo@redhat.com, dave.hansen@linux.intel.com,
kevin.shu@intel.com
Subject: Re: [PATCH RFC v1 0/8] x86/microcode: Enable uniform feature
Date: Tue, 29 Sep 2026 11:47:20 -0700 [thread overview]
Message-ID: <20260929184720.GAarwHuPvasUi-KMaX@fat_crate.local> (raw)
In-Reply-To: <4e801667-d494-411a-be86-dce4b953a114@intel.com>
On Wed, Sep 16, 2026 at 11:10:19PM +0000, Chang S. Bae wrote:
> == Introduction ==
>
> Intel introduces a new microcode loading feature - "uniform". With this
> feature, loading microcode from one logical CPU can update the whole socket
> or the entire system. The hardware implementation works as follows:
>
> <-- paste the appendix here
>
> Then, I guess I may say something about its side-effect which in fact is one
> of the motivation to support this feature. Could be combining next two
> sections into a summary before calling out review points.
Yah, the approach should always be:
Introduce the thing to unenlightened readers. Keep it simple.
Talk about it and implications and blabla.
Ok, loading on an arbitrary thread and getting everyone to upload sounds like
a good simplification for software.
But I guess I'll see how "simple" it really turns out after looking at the
rest.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
prev parent reply other threads:[~2026-09-29 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 0:08 Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 1/8] cpu/hotplug: Allow architecture-specific primary CPU bringup Chang S. Bae
2026-09-30 0:20 ` Borislav Petkov
2026-09-30 4:44 ` Chang S. Bae
2026-09-30 4:57 ` Borislav Petkov
2026-09-12 0:08 ` [PATCH RFC v1 2/8] x86/hotplug: Implement SMT-primary selection for parallel bringup Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 3/8] x86/cpu/topology: Introduce primary core mask Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 4/8] x86/microcode: Extend struct microcode_ops for uniform loading Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 5/8] x86/microcode: Clarify online enforcement with " Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 6/8] x86/microcode: Support uniform scope for late loading Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 7/8] x86/microcode/intel: Support uniform scope for early loading Chang S. Bae
2026-09-12 0:08 ` [PATCH RFC v1 8/8] x86/microcode/intel: Enable uniform loading Chang S. Bae
2026-09-16 0:45 ` [PATCH RFC v1 0/8] x86/microcode: Enable uniform feature Borislav Petkov
2026-09-16 23:10 ` Chang S. Bae
2026-09-29 18:47 ` Borislav Petkov [this message]
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=20260929184720.GAarwHuPvasUi-KMaX@fat_crate.local \
--to=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=kevin.shu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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®