From: Nikolay Borisov <nik.borisov@suse.com>
To: "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 4/9] x86/apic: Implement self-NMI support
Date: Fri, 6 Nov 2026 19:32:02 +0200 [thread overview]
Message-ID: <2b2bae63-6917-4538-b99c-dc2b8656d123@suse.com> (raw)
In-Reply-To: <20261015211426.49114-5-chang.seok.bae@intel.com>
On 16.10.26 г. 0:14 ч., Chang S. Bae wrote:
> From: David Kaplan <david.kaplan@amd.com>
>
> Add a function to send an NMI-to-self which is needed for stop-machine
> NMI facility. Note that send_IPI_self() cannot be used to send an NMI so
> send_IPI() is used.
>
> Signed-off-by: David Kaplan <david.kaplan@amd.com>
> Signed-off-by: Chang S. Bae <chang.seok.bae@intel.com>
This patch should come before patch 2, as it's a building block for it
or since it's small enough it can be part of patch 2.
<snip>
next prev parent reply other threads:[~2026-11-06 17:32 UTC|newest]
Thread overview: 15+ 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-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 [this message]
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=2b2bae63-6917-4538-b99c-dc2b8656d123@suse.com \
--to=nik.borisov@suse.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--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®