From: dave.long@linaro.org (David Long)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] arm64:ftrace: add save_stack_trace_regs()
Date: Thu, 1 Sep 2016 16:38:20 -0400 [thread overview]
Message-ID: <57C891BC.7030502@linaro.org> (raw)
In-Reply-To: <4f7d7a6bff7f06f814bf9a2bdc90bb0e3b833b66.1472734699.git.panand@redhat.com>
On 09/01/2016 09:35 AM, Pratyush Anand wrote:
> Implement save_stack_trace_regs, so that stacktrace of a kprobe events can be
> obtained.
>
> Signed-off-by: Pratyush Anand <panand@redhat.com>
> ---
> V1 to V2: Rebased to latest kernel.
>
> I see following stack trace for kprobe at xhci_irq():
>
> echo stacktrace > /sys/kernel/debug/tracing/trace_options
> echo "p xhci_irq" > /sys/kernel/debug/tracing/kprobe_events
> echo 1 > /sys/kernel/debug/tracing/events/kprobes/enable
> more /sys/kernel/debug/tracing/trace
>
> <idle>-0 [004] d.h. 1356.000496: p_xhci_irq_0:(xhci_irq+0x0/0x9ac)
> <idle>-0 [004] d.h. 1356.000497: <stack trace>
> => xhci_irq
> => __handle_irq_event_percpu
> => handle_irq_event_percpu
> => handle_irq_event
> => handle_fasteoi_irq
> => generic_handle_irq
> => __handle_domain_irq
> => gic_handle_irq
> => el1_irq
> => arch_cpu_idle
> => default_idle_call
> => cpu_startup_entry
> => secondary_start_kernel
> =>
>
> arch/arm64/kernel/stacktrace.c | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/arch/arm64/kernel/stacktrace.c b/arch/arm64/kernel/stacktrace.c
> index d9751a4769e7..bd6d9d8087f0 100644
> --- a/arch/arm64/kernel/stacktrace.c
> +++ b/arch/arm64/kernel/stacktrace.c
> @@ -152,6 +152,24 @@ static int save_trace(struct stackframe *frame, void *d)
> return trace->nr_entries >= trace->max_entries;
> }
>
> +void save_stack_trace_regs(struct pt_regs *regs, struct stack_trace *trace)
> +{
> + struct stack_trace_data data;
> + struct stackframe frame;
> +
> + data.trace = trace;
> + data.skip = trace->skip;
> + data.no_sched_functions = 0;
> +
> + frame.fp = regs->regs[29];
> + frame.sp = regs->sp;
> + frame.pc = regs->pc;
Interesting that arm64 does not define an "lr" field in struct
stackframe like 32-bit arm does.
> +
> + walk_stackframe(current, &frame, save_trace, &data);
> + if (trace->nr_entries < trace->max_entries)
> + trace->entries[trace->nr_entries++] = ULONG_MAX;
> +}
> +
> void save_stack_trace_tsk(struct task_struct *tsk, struct stack_trace *trace)
> {
> struct stack_trace_data data;
>
Looks OK to me. I successfully (if briefly) tested it with v4.8-rc4 on
hikey.
Thanks,
-dl
next prev parent reply other threads:[~2016-09-01 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 13:35 [PATCH V2] arm64:ftrace: add save_stack_trace_regs() Pratyush Anand
2016-09-01 20:38 ` David Long [this message]
2016-09-02 10:50 ` James Morse
2016-09-02 10:56 ` James Morse
2016-09-02 10:59 ` 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=57C891BC.7030502@linaro.org \
--to=dave.long@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).