From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
bpf@vger.kernel.org, x86@kernel.org
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andrii Nakryiko <andrii@kernel.org>,
Indu Bhagat <indu.bhagat@oracle.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
Beau Belgrave <beaub@linux.microsoft.com>,
Jens Remus <jremus@linux.ibm.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v10 07/11] perf: Support deferred user callchains for per CPU events
Date: Sat, 14 Jun 2025 22:41:07 -0400 [thread overview]
Message-ID: <20250614224107.5dfc9f9b@batman.local.home> (raw)
In-Reply-To: <20250614024716.798086123@goodmis.org>
On Fri, 13 Jun 2025 22:46:12 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> +/*
> + * Deferred unwinding callback for per CPU events.
> + * Note, the request for the deferred unwinding may have happened
> + * on a different CPU.
> + */
> +static void perf_event_deferred_cpu(struct unwind_work *work,
> + struct unwind_stacktrace *trace, u64 timestamp)
> +{
> + struct perf_unwind_deferred *defer =
> + container_of(work, struct perf_unwind_deferred, unwind_work);
> + struct perf_unwind_cpu *cpu_events, *cpu_unwind;
> + struct perf_event *event;
> + int cpu;
> +
> + guard(rcu)();
> + guard(preempt)();
> +
> + cpu = smp_processor_id();
> + cpu_events = rcu_dereference(defer->cpu_events);
> + cpu_unwind = &cpu_events[cpu];
> +
> + WRITE_ONCE(cpu_unwind->processing, 1);
> + /*
> + * Make sure the above is seen before the event->unwind_deferred
> + * is checked. This matches the mb() in rcuwait_rcu_wait_event() in
> + * perf_remove_unwind_deferred().
> + */
> + smp_mb();
> +
> + list_for_each_entry_rcu(event, &cpu_unwind->list, unwind_list) {
> + /* If unwind_deferred is NULL the event is going away */
> + if (unlikely(!event->unwind_deferred))
> + continue;
> + perf_event_callchain_deferred(event, trace, timestamp);
> + /* Only the first CPU event gets the trace */
> + break;
> + }
> +
Hmm, I think I need a smp_mb() here too.
> + WRITE_ONCE(cpu_unwind->processing, 0);
> + rcuwait_wake_up(&cpu_unwind->pending_unwind_wait);
> +}
The first smp_mb() is for synchronizing removing of the event from
perf_remove_unwind_deferred() that has:
event->unwind_deferred = NULL;
/*
* Make sure perf_event_deferred_cpu() is done with this event.
* That function will set cpu_unwind->processing and then
* call smp_mb() before iterating the list of its events.
* If the event's unwind_deferred is NULL, it will be skipped.
* The smp_mb() in that function matches the mb() in
* rcuwait_wait_event().
*/
rcuwait_wait_event(&cpu_unwind->pending_unwind_wait,
!cpu_unwind->processing, TASK_UNINTERRUPTIBLE);
So that the unwind_deferred setting to NULL is seen before the
cpu_unwind->processing is checked. But I think, in theory, without the
smp_mb() before the clearing of the cpu_unwind->procssing that it can
be seen before the unwind_deferred is read.
CPU 0 CPU 1
----- -----
read event->unwind_deferred
write NULL > event->unwind_deferre
smp_mb() (in rcuwait)
CPU writes 0 > cpu_unwind->processing (re-ordered)
reads cpu_unwind->processing == 0
Starts to free event
Executes perf_event_callchain_deferred()
I'll add another smp_mb() to be safe in v11.
-- Steve
next prev parent reply other threads:[~2025-06-15 2:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 2:46 [PATCH v10 00/11] perf: Support the deferred unwinding infrastructure Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 01/11] perf: Remove get_perf_callchain() init_nr argument Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 02/11] perf: Have get_perf_callchain() return NULL if crosstask and user are set Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 03/11] perf: Use current->flags & PF_KTHREAD instead of current->mm == NULL Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 04/11] perf: Simplify get_perf_callchain() user logic Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 05/11] perf: Skip user unwind if the task is a kernel thread Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 06/11] perf: Support deferred user callchains Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 07/11] perf: Support deferred user callchains for per CPU events Steven Rostedt
2025-06-15 2:41 ` Steven Rostedt [this message]
2025-06-14 2:46 ` [PATCH v10 08/11] perf tools: Minimal CALLCHAIN_DEFERRED support Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 09/11] perf record: Enable defer_callchain for user callchains Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 10/11] perf script: Display PERF_RECORD_CALLCHAIN_DEFERRED Steven Rostedt
2025-06-14 2:46 ` [PATCH v10 11/11] perf tools: Merge deferred user callchains Steven Rostedt
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=20250614224107.5dfc9f9b@batman.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=indu.bhagat@oracle.com \
--cc=jemarch@gnu.org \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).