mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Chang S. Bae" <chang.seok.bae@intel.com>
To: Nikolay Borisov <nik.borisov@suse.com>,
	"Chang S. Bae" <chang.seok.bae@intel.com>,
	<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>
Subject: Re: [PATCH v3 2/9] stop_machine: Add NMI-based execution path
Date: Mon, 9 Nov 2026 18:06:47 -0800	[thread overview]
Message-ID: <1944bd56-201a-4184-af7c-616e282cc953@intel.com> (raw)
In-Reply-To: <bfe8f403-06c9-4e93-9bcb-738c9128c557@suse.com>

On 11/6/26 09:44, Nikolay Borisov wrote:
> 
> I think this function should be moved over to patch 5 and by having 
> moved/subsumed patch 4, Patch 5 should become patch 3 really so related 
> functionality is introduced in subsequent patches.

Yeah, the suggestion makes sense to me.

On top of this fix,
	https://lore.kernel.org/lkml/d81a45f9-1ba2-4eed-92f2-c5152c5caa7b@intel.com/

my local pile now has:

  * x86/microcode: Remove microcode_nmi_handler_enable
  * x86/nmi: Simplify offline microcode handler invocation
  * x86/microcode: Use stop-machine NMI facility
  * x86/microcode: Distinguish NMI control path on stop-machine callback
  * stop_machine: Introduce stop_machine_nmi_cpuslocked()
  * stop_machine: Add NMI-based execution path
  * x86/nmi: Support NMI stop-machine handler
  * x86/apic: Implement self-NMI support
  * stop_machine: Define build option for NMI stop-machine
  * stop_machine: Refactor multi-CPU stop glue code

I'll post a revision once sorting out the bugfix part and other feedback.

Thanks,
Chang

  reply	other threads:[~2026-11-10  2:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 21:14 [PATCH v3 0/9] x86/microcode: Refactor NMI-based rendezvous mechanism to stop-machine Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 1/9] stop_machine: Refactor multi-CPU stop glue code Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 2/9] stop_machine: Add NMI-based execution path Chang S. Bae
2026-11-06 17:44   ` Nikolay Borisov
2026-11-10  2:06     ` Chang S. Bae [this message]
2026-11-10  2:30       ` Borislav Petkov
2026-10-15 21:14 ` [PATCH v3 3/9] stop_machine: Introduce stop_machine_nmi_cpuslocked() Chang S. Bae
2026-10-16  7:15   ` kernel test robot
2026-10-16 13:46   ` Chang S. Bae
2026-11-06 17:45   ` Nikolay Borisov
2026-10-15 21:14 ` [PATCH v3 4/9] x86/apic: Implement self-NMI support Chang S. Bae
2026-11-06 17:32   ` Nikolay Borisov
2026-10-15 21:14 ` [PATCH v3 5/9] x86/nmi: Support NMI stop-machine handler Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 6/9] x86/microcode: Distinguish NMI control path on stop-machine callback Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 7/9] x86/microcode: Use stop-machine NMI facility Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 8/9] x86/nmi: Simplify offline microcode handler invocation Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 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=1944bd56-201a-4184-af7c-616e282cc953@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=nik.borisov@suse.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®