From: Steven Rostedt <rostedt@kernel.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>,
Arnaldo Carvalho de Melo <acme@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>,
Florian Weimer <fweimer@redhat.com>, Sam James <sam@gentoo.org>,
Kees Cook <kees@kernel.org>,
"Carlos O'Donell" <codonell@redhat.com>
Subject: [PATCH v16 0/4] perf tool: Support the deferred unwinding infrastructure
Date: Mon, 08 Sep 2025 13:53:19 -0400 [thread overview]
Message-ID: <20250908175319.841517121@kernel.org> (raw)
This is the user space side of perf changes to handle deferred unwinding.
It is based on the kernel side of perf patch series here:
https://lore.kernel.org/linux-trace-kernel/20250908171412.268168931@kernel.org/
Changes since v15: https://lore.kernel.org/linux-trace-kernel/20250825180638.877627656@kernel.org/
- Separate out the kernel changes from the user space changes of perf.
- Have the matching deferred code only skip when TID does not match.
Otherwise, process the sample but do not merge if the cookies do not match.
(Namhyung Kim)
Namhyung Kim (4):
perf tools: Minimal CALLCHAIN_DEFERRED support
perf record: Enable defer_callchain for user callchains
perf script: Display PERF_RECORD_CALLCHAIN_DEFERRED
perf tools: Merge deferred user callchains
----
tools/lib/perf/include/perf/event.h | 8 +++
tools/perf/Documentation/perf-script.txt | 5 ++
tools/perf/builtin-script.c | 92 +++++++++++++++++++++++++++++++
tools/perf/util/callchain.c | 24 ++++++++
tools/perf/util/callchain.h | 3 +
tools/perf/util/event.c | 1 +
tools/perf/util/evlist.c | 1 +
tools/perf/util/evlist.h | 1 +
tools/perf/util/evsel.c | 42 ++++++++++++++
tools/perf/util/evsel.h | 1 +
tools/perf/util/machine.c | 1 +
tools/perf/util/perf_event_attr_fprintf.c | 1 +
tools/perf/util/sample.h | 4 +-
tools/perf/util/session.c | 81 +++++++++++++++++++++++++++
tools/perf/util/tool.c | 2 +
tools/perf/util/tool.h | 4 +-
16 files changed, 269 insertions(+), 2 deletions(-)
next reply other threads:[~2025-09-08 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 17:53 Steven Rostedt [this message]
2025-09-08 17:53 ` [PATCH v16 1/4] perf tools: Minimal CALLCHAIN_DEFERRED support Steven Rostedt
2025-09-08 17:53 ` [PATCH v16 2/4] perf record: Enable defer_callchain for user callchains Steven Rostedt
2025-09-08 17:53 ` [PATCH v16 3/4] perf script: Display PERF_RECORD_CALLCHAIN_DEFERRED Steven Rostedt
2025-09-08 17:53 ` [PATCH v16 4/4] perf tools: Merge deferred user callchains Steven Rostedt
2025-10-02 17:49 ` Steven Rostedt
2025-10-24 13:02 ` Peter Zijlstra
2025-10-29 0:09 ` Steven Rostedt
2025-10-29 10:38 ` Peter Zijlstra
2025-10-24 13:01 ` [PATCH v16 0/4] perf tool: Support the deferred unwinding infrastructure Peter Zijlstra
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=20250908175319.841517121@kernel.org \
--to=rostedt@kernel.org \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=codonell@redhat.com \
--cc=fweimer@redhat.com \
--cc=indu.bhagat@oracle.com \
--cc=jemarch@gnu.org \
--cc=jolsa@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=jremus@linux.ibm.com \
--cc=kees@kernel.org \
--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=sam@gentoo.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).