From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@kernel.org, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, peterz@infradead.org,
david.kaplan@amd.com, chang.seok.bae@intel.com
Subject: [PATCH v4 0/9] x86/microcode: Refactor NMI-based rendezvous mechanism to stop-machine
Date: Wed, 4 Nov 2026 18:23:13 +0000 [thread overview]
Message-ID: <20261104182322.578066-1-chang.seok.bae@intel.com> (raw)
Hi all,
This revision has a couple of minor changes on top of 7.4-rc1:
* Remove the fallback prototype (patch3)
* Add a comment at the stop-machine's NMI handler call site (patch5)
V3 previously included several changes addressing Sashiko's feedback. For
the background and overall design, please refer to the more detailed V2
cover [*].
I'll first wait to see whether there is any further feedback from
Sashiko. Otherwise, I think this series is getting close to being ready.
The series is also available in this repository:
git://github.com/intel-staging/microcode.git nmi-stop-machine_v4
Thanks,
Chang
[*] https://lore.kernel.org/20260331014251.86353-12-chang.seok.bae@intel.com
Chang S. Bae (7):
stop_machine: Refactor multi-CPU stop glue code
stop_machine: Add NMI-based execution path
stop_machine: Introduce stop_machine_nmi_cpuslocked()
x86/microcode: Distinguish NMI control path on stop-machine callback
x86/microcode: Use stop-machine NMI facility
x86/nmi: Simplify offline microcode handler invocation
x86/microcode: Remove microcode_nmi_handler_enable
David Kaplan (2):
x86/apic: Implement self-NMI support
x86/nmi: Support NMI stop-machine handler
arch/Kconfig | 3 +
arch/x86/Kconfig | 1 +
arch/x86/include/asm/microcode.h | 11 --
arch/x86/kernel/apic/ipi.c | 10 ++
arch/x86/kernel/cpu/microcode/core.c | 35 ++----
arch/x86/kernel/nmi.c | 12 +-
include/linux/stop_machine.h | 38 ++++++
kernel/stop_machine.c | 180 ++++++++++++++++++++++++---
8 files changed, 232 insertions(+), 58 deletions(-)
base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
--
2.53.0
next reply other threads:[~2026-11-04 18:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 18:23 Chang S. Bae [this message]
2026-11-04 18:23 ` [PATCH v4 1/9] stop_machine: Refactor multi-CPU stop glue code Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 2/9] stop_machine: Add NMI-based execution path Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 3/9] stop_machine: Introduce stop_machine_nmi_cpuslocked() Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 4/9] x86/apic: Implement self-NMI support Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 5/9] x86/nmi: Support NMI stop-machine handler Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 6/9] x86/microcode: Distinguish NMI control path on stop-machine callback Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 7/9] x86/microcode: Use stop-machine NMI facility Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 8/9] x86/nmi: Simplify offline microcode handler invocation Chang S. Bae
2026-11-04 21:56 ` Chang S. Bae
2026-11-04 18:23 ` [PATCH v4 9/9] x86/microcode: Remove microcode_nmi_handler_enable Chang S. Bae
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=20261104182322.578066-1-chang.seok.bae@intel.com \
--to=chang.seok.bae@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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®