[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZVubargzvLPmhSYd@FVFF77S0Q05N.cambridge.arm.com>
Date: Mon, 20 Nov 2023 17:46:18 +0000
From: Mark Rutland <mark.rutland@....com>
To: qiwuchen55@...il.com
Cc: catalin.marinas@....com, will@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
chenqiwu <qiwu.chen@...nssion.com>
Subject: Re: [PATCH] arm64: Add user stacktrace support
On Mon, Nov 20, 2023 at 02:29:23PM +0000, Mark Rutland wrote:
> On Sat, Nov 18, 2023 at 09:45:04PM +0800, qiwuchen55@...il.com wrote:
> > From: chenqiwu <qiwu.chen@...nssion.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.
Powered by blists - more mailing lists