The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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: [PATCH v9 00/11] perf: Support the deferred unwinding infrastructure
Date: Tue, 10 Jun 2025 21:34:21 -0400	[thread overview]
Message-ID: <20250611013421.040264741@goodmis.org> (raw)


This is based on top of the deferred unwind core patch series:

  https://lore.kernel.org/linux-trace-kernel/20250611005421.144238328@goodmis.org/

Which is based on top of v6.16-rc1.

This series implements the perf interface to use deferred user space stack
tracing. I'm posting this now for review and comments and a way for people to
test out the unwind deferred core series. As this has updates to user ABI it
should be scrutinized much more as once this is accepted it is set in stone.
This is why this is a separate patch series.

Changes since v8: https://lore.kernel.org/linux-trace-kernel/20250509164524.448387100@goodmis.org/

- Simply rebased on top of the latest unwind deferred core.

- This still has issues that were brought up in v8 by Andii regarding
  cross_task and user vs kernel stack tracing. I did not yet address these
  concerns as I just wanted to get this series out based on v6.16-rc*.

  https://lore.kernel.org/linux-trace-kernel/CAEf4BzaKfvCu2T+jJ2e-CCt0N50urfx+p6kQfV899_jkmT_XKQ@mail.gmail.com/

Josh Poimboeuf (5):
      perf: Remove get_perf_callchain() init_nr argument
      perf: Have get_perf_callchain() return NULL if crosstask and user are set
      perf: Simplify get_perf_callchain() user logic
      perf: Skip user unwind if the task is a kernel thread
      perf: Support deferred user callchains

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

Steven Rostedt (2):
      perf: Use current->flags & PF_KTHREAD instead of current->mm == NULL
      perf: Support deferred user callchains for per CPU events

----
 arch/Kconfig                              |   3 +
 include/linux/perf_event.h                |  14 +-
 include/uapi/linux/perf_event.h           |  19 +-
 kernel/bpf/stackmap.c                     |   8 +-
 kernel/events/callchain.c                 |  47 ++--
 kernel/events/core.c                      | 352 +++++++++++++++++++++++++++++-
 tools/include/uapi/linux/perf_event.h     |  19 +-
 tools/lib/perf/include/perf/event.h       |   7 +
 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                   |  39 ++++
 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                  |   3 +-
 tools/perf/util/session.c                 |  78 +++++++
 tools/perf/util/tool.c                    |   2 +
 tools/perf/util/tool.h                    |   4 +-
 23 files changed, 691 insertions(+), 34 deletions(-)

             reply	other threads:[~2025-06-11  1:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  1:34 Steven Rostedt [this message]
2025-06-11  1:34 ` [PATCH v9 01/11] perf: Remove get_perf_callchain() init_nr argument Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 02/11] perf: Have get_perf_callchain() return NULL if crosstask and user are set Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 03/11] perf: Use current->flags & PF_KTHREAD instead of current->mm == NULL Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 04/11] perf: Simplify get_perf_callchain() user logic Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 05/11] perf: Skip user unwind if the task is a kernel thread Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 06/11] perf: Support deferred user callchains Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 07/11] perf tools: Minimal CALLCHAIN_DEFERRED support Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 08/11] perf record: Enable defer_callchain for user callchains Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 09/11] perf script: Display PERF_RECORD_CALLCHAIN_DEFERRED Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 10/11] perf tools: Merge deferred user callchains Steven Rostedt
2025-06-11  1:34 ` [PATCH v9 11/11] perf: Support deferred user callchains for per CPU events 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=20250611013421.040264741@goodmis.org \
    --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