From: Steven Rostedt <rostedt@goodmis.org>
To: Petr Tesarik <ptesarik@suse.com>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH] ring-buffer: Use a housekeeping CPU to wake up waiters
Date: Wed, 7 Jan 2026 11:17:09 -0500 [thread overview]
Message-ID: <20260107111709.0d115cd8@gandalf.local.home> (raw)
In-Reply-To: <20260107105137.4cf9a67e@mordecai>
On Wed, 7 Jan 2026 10:51:37 +0100
Petr Tesarik <ptesarik@suse.com> wrote:
> Erm. It's actually good I had a look. :-(
>
> A helpful comment in irq_work_queue_on() explains that "arch remote IPI
> send/receive backend aren't NMI safe". That's something I wasn't aware
> of, and I'm afraid it's the end of story. The comment is followed by a
> WARN_ON_ONCE(in_nmi()), and I can easily trigger it with "perf top"
> while nmi:nmi_handler is traced.
>
> Please, remove the patch again. I'm sorry.
Or we simply change it to:
static inline void
rb_irq_work_queue(struct rb_irq_work *irq_work)
{
int cpu;
/* irq_work_queue_on() is not allowed in NMI context */
if (in_nmi()) {
irq_work_queue(&irq_work->work, cpu);
return;
}
cpu = housekeeping_any_cpu(HK_TYPE_KERNEL_NOISE);
/*
* If CPU isolation is not active, cpu is always the current
* CPU, and the following is equivallent to irq_work_queue().
*/
irq_work_queue_on(&irq_work->work, cpu);
}
-- Steve
next prev parent reply other threads:[~2026-01-07 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 9:10 [PATCH] ring-buffer: Use a housekeeping CPU to wake up waiters Petr Tesarik
2026-01-06 22:04 ` Steven Rostedt
2026-01-07 7:50 ` Petr Tesarik
2026-01-07 9:51 ` Petr Tesarik
2026-01-07 16:17 ` Steven Rostedt [this message]
2026-01-07 16:19 ` Steven Rostedt
2026-01-08 8:39 ` Petr Tesarik
2026-01-08 10:46 ` Petr Tesarik
2026-01-08 16:58 ` Steven Rostedt
2026-01-09 8:57 ` Petr Tesarik
2026-01-09 16:15 ` Steven Rostedt
2026-01-09 16:54 ` Petr Tesarik
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=20260107111709.0d115cd8@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=clrkwllms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=ptesarik@suse.com \
/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