From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, will@kernel.org, arnd@arndb.de,
afd@ti.com, linus.walleij@linaro.org, akpm@linux-foundation.org,
masahiroy@kernel.org, eric.devolder@oracle.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v2] ARM: stacktrace: Add USER_STACKTRACE support
Date: Fri, 2 Aug 2024 12:48:16 +0100 [thread overview]
Message-ID: <ZqzHgFB2t+SWy5o9@shell.armlinux.org.uk> (raw)
In-Reply-To: <20240730021532.1752582-1-ruanjinjie@huawei.com>
On Tue, Jul 30, 2024 at 10:15:32AM +0800, Jinjie Ruan wrote:
> Currently, userstacktrace is unsupported for ARM. So use the
> perf_callchain_user() code as blueprint to implement the
> arch_stack_walk_user() which add userstacktrace support on ARM.
> Meanwhile, we can use arch_stack_walk_user() to simplify the implementation
> of perf_callchain_user().
>
> A ftrace test case is shown as below:
> # cd /sys/kernel/debug/tracing
> # echo 1 > options/userstacktrace
> # echo 1 > options/sym-userobj
> # echo 1 > events/sched/sched_process_fork/enable
> # cat trace
>
> ......
> sh-100 [000] ..... 51.779261: sched_process_fork: comm=sh pid=100 child_comm=sh child_pid=108
> sh-100 [000] ..... 51.779285: <user stack trace>
> => /lib/libc.so.6[+0xb3c8c]
> => /bin/busybox[+0xffb901f1]
>
> Also a simple perf test is ok as below:
> # perf record -e cpu-clock --call-graph fp top
> # perf report --call-graph
>
> .....
> [[31m 65.00%[[m 0.00% top [kernel.kallsyms] [k] __ret_fast_syscall
>
> |
> ---__ret_fast_syscall
> |
> |--[[31m30.00%[[m--__se_sys_getdents64
> | iterate_dir
> | |
> | |--[[31m25.00%[[m--proc_pid_readdir
>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
Do you have a use case for this feature?
Given that userspace is free to do whatever it likes with stack frames,
I think this is going to be hit and miss whether it works.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-08-02 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-30 2:15 [PATCH v2] ARM: stacktrace: Add USER_STACKTRACE support Jinjie Ruan
2024-08-02 11:48 ` Russell King (Oracle) [this message]
2024-08-12 6:45 ` Jinjie Ruan
2024-08-12 15:02 ` Russell King (Oracle)
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=ZqzHgFB2t+SWy5o9@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=afd@ti.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=arnd@arndb.de \
--cc=eric.devolder@oracle.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=masahiroy@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=ruanjinjie@huawei.com \
--cc=will@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).