From: Mark Rutland <mark.rutland@arm.com>
To: qiwuchen55@gmail.com
Cc: catalin.marinas@arm.com, will@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, chenqiwu <qiwu.chen@transsion.com>
Subject: Re: [PATCH] arm64: Add user stacktrace support
Date: Mon, 20 Nov 2023 17:46:18 +0000 [thread overview]
Message-ID: <ZVubargzvLPmhSYd@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <ZVttPU64cCem6szI@FVFF77S0Q05N.cambridge.arm.com>
On Mon, Nov 20, 2023 at 02:29:23PM +0000, Mark Rutland wrote:
> On Sat, Nov 18, 2023 at 09:45:04PM +0800, qiwuchen55@gmail.com wrote:
> > From: chenqiwu <qiwu.chen@transsion.com>
> > 2. Add arch_stack_walk_user() implementation to support userstacktrace transsionce option.
>
> What is this 'userstacktrace transsionce option' ?
Sorry, I evidently corrupted the mail at my end; "transsionce" was "trace" in
the original mail, which matches the ftrace output below.
Please ignore this specific comment; my other concerns still apply.
> > A example test about the output format of ftrace userstacktrace as shown below:
> > bash-489 [000] ..... 2167.660775: sched_process_fork: comm=bash pid=489 child_comm=bash child_pid=596
> > bash-489 [000] ..... 2167.660787: <user stack trace>
> > => /lib/aarch64-linux-gnu/libc-2.32.so[+0xa76d8]
> > => /bin/bash[+0x5f354]
> > => /bin/bash[+0x4876c]
> > => /bin/bash[+0x4aec4]
> > => /bin/bash[+0x4da48]
> > => /bin/bash[+0x4b710]
> > => /bin/bash[+0x4c31c]
> > => /bin/bash[+0x339b0]
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-11-20 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 13:45 [PATCH] arm64: Add user stacktrace support qiwuchen55
2023-11-18 20:40 ` kernel test robot
2023-11-20 14:29 ` Mark Rutland
2023-11-20 17:46 ` Mark Rutland [this message]
2023-11-21 9:03 ` chenqiwu
2023-11-21 14:05 ` Mark Rutland
2023-11-24 9:55 ` chenqiwu
2023-11-24 10:12 ` Mark Rutland
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=ZVubargzvLPmhSYd@FVFF77S0Q05N.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qiwu.chen@transsion.com \
--cc=qiwuchen55@gmail.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