From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sam James <sam@gentoo.org>,
fweimer@redhat.com, akpm@linux-foundation.org, andrii@kernel.org,
axboe@kernel.dk, beaub@linux.microsoft.com, bpf@vger.kernel.org,
indu.bhagat@oracle.com, jemarch@gnu.org, jolsa@kernel.org,
jpoimboe@kernel.org, jremus@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
mingo@kernel.org, peterz@infradead.org, tglx@linutronix.de,
torvalds@linux-foundation.org, x86@kernel.org
Subject: Re: [PATCH v11 00/14] unwind_user: x86: Deferred unwinding infrastructure
Date: Wed, 2 Jul 2025 10:14:29 -0700 [thread overview]
Message-ID: <aGVo9b1xiT1Moq-P@google.com> (raw)
In-Reply-To: <20250702121502.6e9d6102@batman.local.home>
On Wed, Jul 02, 2025 at 12:15:02PM -0400, Steven Rostedt wrote:
> On Wed, 02 Jul 2025 12:44:51 +0100
> Sam James <sam@gentoo.org> wrote:
>
> > In one of the commit messages in the perf series, Steven also gave
> > `perf record -g -vv true` which was convenient for making sure it's
> > correctly discovered deferred unwinding support.
>
> Although I posted the patch, the command "perf record -g -vv true" was
> Namhyung's idea. Just wanted to give credit where credit was due.
Yep, it's to check if perf tool ask the deferred callchain to the
kernel. To check if the kernel returns the callchain properly is:
$ perf report -D | grep -A5 CALLCHAIN_DEFERRED
Thanks,
Namhyung
next prev parent reply other threads:[~2025-07-02 17:14 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 22:56 [PATCH v11 00/14] unwind_user: x86: Deferred unwinding infrastructure Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 01/14] unwind_user: Add user space unwinding API Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 02/14] unwind_user: Add frame pointer support Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 03/14] unwind_user: Add compat mode " Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 04/14] unwind_user/deferred: Add unwind_user_faultable() Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 05/14] unwind_user/deferred: Add unwind cache Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 06/14] unwind_user/deferred: Add deferred unwinding interface Steven Rostedt
2025-06-26 16:48 ` Steven Rostedt
2025-06-26 20:34 ` Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 07/14] unwind_user/deferred: Make unwind deferral requests NMI-safe Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 08/14] unwind deferred: Use bitmask to determine which callbacks to call Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 09/14] unwind deferred: Use SRCU unwind_deferred_task_work() Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 10/14] unwind: Clear unwind_mask on exit back to user space Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 11/14] unwind: Finish up unwind when a task exits Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 12/14] unwind_user/x86: Enable frame pointer unwinding on x86 Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 13/14] perf/x86: Rename and move get_segment_base() and make it global Steven Rostedt
2025-06-26 8:44 ` Ingo Molnar
2025-06-26 12:13 ` Steven Rostedt
2025-06-26 13:07 ` Peter Zijlstra
2025-06-26 15:13 ` Steven Rostedt
2025-06-25 22:56 ` [PATCH v11 14/14] unwind_user/x86: Enable compat mode frame pointer unwinding on x86 Steven Rostedt
2025-06-26 8:33 ` Ingo Molnar
2025-06-26 12:12 ` Steven Rostedt
2025-06-27 14:01 ` Steven Rostedt
2025-06-27 16:23 ` Linus Torvalds
2025-06-30 12:50 ` [PATCH v11 00/14] unwind_user: x86: Deferred unwinding infrastructure Florian Weimer
2025-06-30 16:35 ` Namhyung Kim
2025-06-30 17:30 ` Steven Rostedt
2025-07-02 11:44 ` Sam James
2025-07-02 16:15 ` Steven Rostedt
2025-07-02 17:14 ` Namhyung Kim [this message]
2025-07-03 4:01 ` Sam James
2025-07-02 17:10 ` Namhyung Kim
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=aGVo9b1xiT1Moq-P@google.com \
--to=namhyung@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=axboe@kernel.dk \
--cc=beaub@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--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=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=peterz@infradead.org \
--cc=rostedt@goodmis.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).