From: Thomas Gleixner <tglx@linutronix.de>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
x86@kernel.org, "Chang S. Bae" <chang.seok.bae@intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Nikolay Borisov <nik.borisov@suse.com>
Subject: Re: [patch V3 21/30] x86/microcode: Add per CPU result state
Date: Tue, 26 Sep 2023 11:09:01 +0200 [thread overview]
Message-ID: <87sf71fgia.ffs@tglx> (raw)
In-Reply-To: <20230924062934.GLZQ/XThoM7jsrjmrt@fat_crate.local>
On Sun, Sep 24 2023 at 08:29, Borislav Petkov wrote:
> On Tue, Sep 12, 2023 at 09:58:16AM +0200, Thomas Gleixner wrote:
>> +struct ucode_ctrl {
>
> microcode_ctrl
>
> I know "ucode" is shorter but we already call everything new-er
> "microcode_" and this'll cause confusion.
That starts to get silly. The struct is used only in the microcode realm
and nothing which is globally visible. ucode is a pretty obvious and
established shortcut. But so what....
>> + enum ucode_state result;
>> +};
>> +
>> +static DEFINE_PER_CPU(struct ucode_ctrl, ucode_ctrl);
>
> You could do
>
> static DEFINE_PER_CPU(struct microcode_ctrl, ucode_ctrl);
>
> so that the naming is different too.
And that solves what?
>> static atomic_t late_cpus_in, late_cpus_out;
>>
>> static bool wait_for_cpus(atomic_t *cnt)
>> @@ -344,23 +349,19 @@ static bool wait_for_cpus(atomic_t *cnt)
>> return false;
>> }
>>
>> -/*
>> - * Returns:
>> - * < 0 - on error
>> - * 0 - success (no update done or microcode was updated)
>> - */
>> -static int __reload_late(void *info)
>> +static int ucode_load_cpus_stopped(void *unused)
>
> No need for "ucode_" prefixes to static functions.
What's the problem with that prefix? The function name clearly says what
this is doing.
>> {
>> int cpu = smp_processor_id();
>> - enum ucode_state err;
>> - int ret = 0;
>> + enum ucode_state ret;
>>
>> /*
>> * Wait for all CPUs to arrive. A load will not be attempted unless all
>> * CPUs show up.
>> * */
>> - if (!wait_for_cpus(&late_cpus_in))
>> - return -1;
>> + if (!wait_for_cpus(&late_cpus_in)) {
>> + this_cpu_write(ucode_ctrl.result, UCODE_TIMEOUT);
>> + return 0;
>
> So the only value this function returns is 0 now.
> stop_machine_cpuslocked() still does pay attention at ret so I guess it
> should return non-null/negative on error or so?
Nope, because stop_machine_cpuslocked() does not usefully accumulate
results from all involved CPUs. But it can return errors related to the
invocation itself, which is a completely different story.
That's why ucode_ctrl.result is per CPU and has to be evaluated
separately.
>> - ret = stop_machine_cpuslocked(__reload_late, NULL, cpu_online_mask);
>> + stop_machine_cpuslocked(ucode_load_cpus_stopped, NULL, cpu_online_mask);
>> +
>> + /* Analyze the results */
>> + for_each_cpu_and(cpu, cpu_present_mask, &cpus_booted_once_mask) {
>> + switch (per_cpu(ucode_ctrl.result, cpu)) {
>> + case UCODE_UPDATED: updated++; break;
>> + case UCODE_TIMEOUT: timedout++; break;
>> + case UCODE_OK: siblings++; break;
>> + default: failed++; break;
>> + }
>
> Align vertically.
Align what?
>> + }
>>
>> if (microcode_ops->finalize_late_load)
>> - microcode_ops->finalize_late_load(ret);
>> + microcode_ops->finalize_late_load(!updated);
>>
>> - if (!ret) {
>> - pr_info("Reload succeeded, microcode revision: 0x%x -> 0x%x\n",
>> - old, boot_cpu_data.microcode);
>> - microcode_check(&prev_info);
>> - add_taint(TAINT_CPU_OUT_OF_SPEC, LOCKDEP_STILL_OK);
>> - } else {
>> - pr_info("Reload failed, current microcode revision: 0x%x\n",
>> - boot_cpu_data.microcode);
>> + if (!updated) {
>> + /* Nothing changed. */
>> + if (!failed && !timedout)
>> + return 0;
>> + pr_err("Microcode update failed: %u CPUs failed %u CPUs timed out\n",
>> + failed, timedout);
>> + return -EIO;
>> }
>> - return ret;
>> +
>> + add_taint(TAINT_CPU_OUT_OF_SPEC, LOCKDEP_STILL_OK);
>> + pr_info("Microcode load: updated on %u primary CPUs with %u siblings\n", updated, siblings);
>> + if (failed || timedout) {
>> + pr_err("Microcode load incomplete. %u CPUs timed out or failed\n",
>> + num_online_cpus() - (updated + siblings));
>> + }
>> + pr_info("Microcode revision: 0x%x -> 0x%x\n", old_rev, boot_cpu_data.microcode);
>
> You don't need "Microcode" in those strings - the pr_info has already
> "microcode:" as prefix.
True.
>> @@ -448,9 +463,12 @@ static int microcode_reload_late(void)
>> * behaviour is undefined. The default play_dead() implementation on
>> * modern CPUs is using MWAIT, which is also not guaranteed to be safe
>> * against a microcode update which affects MWAIT.
>> + *
>> + * 2) Initialize the per CPU control structure
>> */
>> -static bool ensure_cpus_are_online(void)
>> +static bool ucode_setup_cpus(void)
>
> s/ucode_//
and setup_cpus() then tells what?
next prev parent reply other threads:[~2023-09-26 16:06 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 7:57 [patch V3 00/30] x86/microcode: Cleanup and late loading enhancements Thomas Gleixner
2023-09-12 7:57 ` [patch V3 01/30] x86/microcode/32: Move early loading after paging enable Thomas Gleixner
2023-09-13 15:06 ` Borislav Petkov
2023-09-16 9:03 ` Chang S. Bae
2023-09-17 19:17 ` Thomas Gleixner
2023-09-19 14:54 ` [patch V3a " Thomas Gleixner
2023-09-12 7:57 ` [patch V3 02/30] x86/boot/32: Disable stackprotector and tracing for mk_early_pgtbl_32() Thomas Gleixner
2023-09-18 17:12 ` Borislav Petkov
2023-09-12 7:57 ` [patch V3 03/30] x86/microcode/intel: Rip out mixed stepping support for Intel CPUs Thomas Gleixner
2023-09-25 15:19 ` Qiuxu Zhuo
2023-09-12 7:57 ` [patch V3 04/30] x86/microcode/intel: Simplify scan_microcode() Thomas Gleixner
2023-09-19 12:52 ` Borislav Petkov
2023-09-12 7:57 ` [patch V3 05/30] x86/microcode/intel: Simplify and rename generic_load_microcode() Thomas Gleixner
2023-09-12 7:57 ` [patch V3 06/30] x86/microcode/intel: Cleanup code further Thomas Gleixner
2023-09-19 14:13 ` Borislav Petkov
2023-09-12 7:57 ` [patch V3 07/30] x86/microcode/intel: Simplify early loading Thomas Gleixner
2023-09-19 14:32 ` Borislav Petkov
2023-09-19 14:57 ` Thomas Gleixner
2023-09-19 17:35 ` Thomas Gleixner
2023-09-12 7:57 ` [patch V3 08/30] x86/microcode/intel: Save the microcode only after a successful late-load Thomas Gleixner
2023-09-20 14:39 ` Borislav Petkov
2023-09-25 15:30 ` Subject: " Qiuxu Zhuo
2023-09-12 7:57 ` [patch V3 09/30] x86/microcode/intel: Switch to kvmalloc() Thomas Gleixner
2023-09-25 15:43 ` Subject: " Qiuxu Zhuo
2023-09-12 7:57 ` [patch V3 10/30] x86/microcode/intel: Unify microcode apply() functions Thomas Gleixner
2023-09-21 10:07 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 11/30] x86/microcode/intel: Rework intel_cpu_collect_info() Thomas Gleixner
2023-09-12 7:58 ` [patch V3 12/30] x86/microcode/intel: Reuse intel_cpu_collect_info() Thomas Gleixner
2023-09-21 10:42 ` Borislav Petkov
2023-09-25 10:47 ` Thomas Gleixner
2023-10-03 14:14 ` Borislav Petkov
2023-10-03 14:23 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 13/30] x86/microcode/intel: Rework intel_find_matching_signature() Thomas Gleixner
2023-09-12 7:58 ` [patch V3 14/30] x86/microcode/amd: Read revision from hardware in collect_cpu_info_amd() Thomas Gleixner
2023-09-12 7:58 ` [patch V3 15/30] x86/microcode: Remove pointless apply() invocation Thomas Gleixner
2023-09-12 7:58 ` [patch V3 16/30] x86/microcode: Get rid of the schedule work indirection Thomas Gleixner
2023-09-12 7:58 ` [patch V3 17/30] x86/microcode: Clean up mc_cpu_down_prep() Thomas Gleixner
2023-09-12 7:58 ` [patch V3 18/30] x86/microcode: Handle "nosmt" correctly Thomas Gleixner
2023-09-22 13:42 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 19/30] x86/microcode: Clarify the late load logic Thomas Gleixner
2023-09-22 15:59 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 20/30] x86/microcode: Sanitize __wait_for_cpus() Thomas Gleixner
2023-09-22 16:24 ` Borislav Petkov
2023-09-26 8:51 ` Thomas Gleixner
2023-09-27 7:56 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 21/30] x86/microcode: Add per CPU result state Thomas Gleixner
2023-09-24 6:29 ` Borislav Petkov
2023-09-26 9:09 ` Thomas Gleixner [this message]
2023-09-27 11:28 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 22/30] x86/microcode: Add per CPU control field Thomas Gleixner
2023-09-24 6:47 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 23/30] x86/microcode: Provide new control functions Thomas Gleixner
2023-09-24 6:58 ` Borislav Petkov
2023-09-26 9:42 ` Thomas Gleixner
2023-09-27 11:50 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 24/30] x86/microcode: Replace the all in one rendevouz handler Thomas Gleixner
2023-09-27 16:47 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 25/30] x86/microcode: Rendezvous and load in NMI Thomas Gleixner
2023-09-27 17:17 ` Borislav Petkov
2023-09-28 9:33 ` Thomas Gleixner
2023-09-12 7:58 ` [patch V3 26/30] x86/microcode: Protect against instrumentation Thomas Gleixner
2023-09-28 10:52 ` Borislav Petkov
2023-09-12 7:58 ` [patch V3 27/30] x86/apic: Provide apic_force_nmi_on_cpu() Thomas Gleixner
2023-09-12 7:58 ` [patch V3 28/30] x86/microcode: Handle "offline" CPUs correctly Thomas Gleixner
2023-09-12 7:58 ` [patch V3 29/30] x86/microcode: Prepare for minimal revision check Thomas Gleixner
2023-09-28 11:47 ` Borislav Petkov
2023-10-02 9:42 ` Thomas Gleixner
2023-09-12 7:58 ` [patch V3 30/30] x86/microcode/intel: Add a minimum required revision for late-loads Thomas Gleixner
2023-09-25 16:20 ` Qiuxu Zhuo
2023-09-25 17:02 ` [patch V3 00/30] x86/microcode: Cleanup and late loading enhancements Qiuxu Zhuo
2023-09-28 12:00 ` Borislav Petkov
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=87sf71fgia.ffs@tglx \
--to=tglx@linutronix.de \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.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