From: Jiping Ma <Jiping.Ma2@windriver.com>
To: Will Deacon <will@kernel.org>
Cc: will.deacon@arm.com, mark.rutland@arm.com,
catalin.marinas@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, peterz@infradead.org,
mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Perf: support to unwind userspace application stacks generated with thumb.
Date: Wed, 22 Apr 2020 10:56:04 +0800 [thread overview]
Message-ID: <01029876-e167-a1ba-cb1a-d97adf23dde4@windriver.com> (raw)
In-Reply-To: <20200416071023.GB29742@willie-the-truck>
On 04/16/2020 03:10 PM, Will Deacon wrote:
> On Thu, Apr 16, 2020 at 01:38:29PM +0800, Jiping Ma wrote:
>> Only push sp and lr in the stack for thumb mode. it will go
>> through the stack find sp and lr.
>>
>> Change this to the more detailed description of the patch
>>
>> Signed-off-by: Jiping Ma <jiping.ma2@windriver.com>
>> ---
>> arch/arm64/kernel/perf_callchain.c | 36 +++++++++++++++++++++++++++---
>> 1 file changed, 33 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/perf_callchain.c b/arch/arm64/kernel/perf_callchain.c
>> index bcafd7dcfe8b..97dde271c121 100644
>> --- a/arch/arm64/kernel/perf_callchain.c
>> +++ b/arch/arm64/kernel/perf_callchain.c
>> @@ -104,6 +104,30 @@ compat_user_backtrace(struct compat_frame_tail __user *tail,
>>
>> return (struct compat_frame_tail __user *)compat_ptr(buftail.fp) - 1;
>> }
>> +
>> +void
>> +user_backtrace_thumb(struct perf_callchain_entry_ctx *entry,
>> + struct pt_regs *regs)
>> +{
>> + u32 sp;
>> + u32 *sp_t;
>> + /*
>> + * Only push sp, lr to stack.
>> + */
>> + for (sp = regs->compat_sp; (sp < current->mm->start_stack) &&
>> + (entry->nr < entry->max_stack); sp += 4) {
>> + sp_t = (u32 *)(unsigned long)sp;
>> + if ((*sp_t > regs->compat_sp) &&
>> + (*sp_t < current->mm->start_stack)) {
>> + if (*(sp_t + 1) < current->mm->end_code &&
>> + *(sp_t + 1) > current->mm->start_code) {
>> + perf_callchain_store(entry, *(sp_t + 1)-1);
>> + sp += 4;
>> + }
>> + }
>> + }
>> +}
> This looks like a pile of fragile heuristics to me. Why don't you just use
> libunwind in userspace, the same way you'd have to if you compiled without
> framepointers?
Hi, Will
Could you share more details for libunwind in userspace? Following is
our build command for test app.
bt_perf.thumb: arm-wrs-linux-gnueabi-gcc -march=armv7ve -mthumb
-mfpu=neon -mfloat-abi=softfp -mcpu=cortex-a15
--sysroot=sysroots/cortexa15t2-neon-wrs-linux-gnueabi -O0 -g -ggdb -Wall
-funwind-tables -fno-omit-frame-pointer -frecord-gcc-switches
-mapcs-frame bt_perf.c -o bt_perf.thumb
Thanks,
Jiping
>
> Will
>
next prev parent reply other threads:[~2020-04-22 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 5:38 Jiping Ma
2020-04-16 7:10 ` Will Deacon
2020-04-22 2:56 ` Jiping Ma [this message]
2020-04-22 8:19 ` Will Deacon
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=01029876-e167-a1ba-cb1a-d97adf23dde4@windriver.com \
--to=jiping.ma2@windriver.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=catalin.marinas@arm.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.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
all inboxes | Powered by JetHome®