From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Synchonise dump_backtrace() with perf callchain
Date: Thu, 15 Oct 2015 18:26:01 +0100 [thread overview]
Message-ID: <20151015172600.GD19202@arm.com> (raw)
In-Reply-To: <1444915314-13649-1-git-send-email-jungseoklee85@gmail.com>
On Thu, Oct 15, 2015 at 01:21:54PM +0000, Jungseok Lee wrote:
> dump_backtrace() has its own backtrace logic unlike perf callchain which
> relies on walk_stackframe(). They behave differently when a symbol is
> recorded. Perf writes it down *before* calling unwind_frame(), but
> dump_backtrace() prints it out *after* unwind_frame(). As a result, the
> last valid symbol is not added to a list in case of dump_backtrace().
>
> This patch catches up the last symbol as synchronising dump_backtrace()
> with perf callchain. However, the patch does not cover a case where MMU
> is disabled. That is, a physical address can be stored in stack frame,
> but it's not handled. For example, a swapper process falls into this case.
> Unlike a swapper from a secondary core, a swapper on a boot cpu, which
> starting from __mmap_switched(), can't be tracked down with a simple
> conversion, phys_to_virt(), because PC is retrieved from LR - 4, not LR.
It would be good to have an example backtrace before and after this patch
is applied, to show what it fixes.
> It is a big tradeoff to change both head.S and unwind_frame() structure
> for a few of symbols in *.S, so this hunk does not take care of the case.
>
> Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Cc: James Morse <james.morse@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> ---
> arch/arm64/kernel/traps.c | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index f93aae5..4ddb928 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -103,12 +103,13 @@ static void dump_mem(const char *lvl, const char *str, unsigned long bottom,
> set_fs(fs);
> }
>
> -static void dump_backtrace_entry(unsigned long where, unsigned long stack)
> +static void dump_backtrace_entry(unsigned long where)
> {
> + /*
> + * The highest stack frame of a swapper process stores PC in a form
> + * of physical address, but this case is not handled.
> + */
> print_ip_sym(where);
> - if (in_exception_text(where))
> - dump_mem("", "Exception stack", stack,
> - stack + sizeof(struct pt_regs), false);
> }
>
> static void dump_instr(const char *lvl, struct pt_regs *regs)
> @@ -172,12 +173,17 @@ static void dump_backtrace(struct pt_regs *regs, struct task_struct *tsk)
> pr_emerg("Call trace:\n");
> while (1) {
> unsigned long where = frame.pc;
> + unsigned long stack;
> int ret;
>
> + dump_backtrace_entry(where);
> ret = unwind_frame(&frame);
> if (ret < 0)
> break;
> - dump_backtrace_entry(where, frame.sp);
> + stack = frame.sp;
> + if (in_exception_text(where))
> + dump_mem("", "Exception stack", stack,
> + stack + sizeof(struct pt_regs), false);
AFAICT, the original code is all based on unwind_backtrace in
arch/arm/kernel/unwind.c. Does that need updating too (as a separate patch)?
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will.deacon@arm.com>
To: Jungseok Lee <jungseoklee85@gmail.com>
Cc: catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
James Morse <james.morse@arm.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] arm64: Synchonise dump_backtrace() with perf callchain
Date: Thu, 15 Oct 2015 18:26:01 +0100 [thread overview]
Message-ID: <20151015172600.GD19202@arm.com> (raw)
In-Reply-To: <1444915314-13649-1-git-send-email-jungseoklee85@gmail.com>
On Thu, Oct 15, 2015 at 01:21:54PM +0000, Jungseok Lee wrote:
> dump_backtrace() has its own backtrace logic unlike perf callchain which
> relies on walk_stackframe(). They behave differently when a symbol is
> recorded. Perf writes it down *before* calling unwind_frame(), but
> dump_backtrace() prints it out *after* unwind_frame(). As a result, the
> last valid symbol is not added to a list in case of dump_backtrace().
>
> This patch catches up the last symbol as synchronising dump_backtrace()
> with perf callchain. However, the patch does not cover a case where MMU
> is disabled. That is, a physical address can be stored in stack frame,
> but it's not handled. For example, a swapper process falls into this case.
> Unlike a swapper from a secondary core, a swapper on a boot cpu, which
> starting from __mmap_switched(), can't be tracked down with a simple
> conversion, phys_to_virt(), because PC is retrieved from LR - 4, not LR.
It would be good to have an example backtrace before and after this patch
is applied, to show what it fixes.
> It is a big tradeoff to change both head.S and unwind_frame() structure
> for a few of symbols in *.S, so this hunk does not take care of the case.
>
> Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Cc: James Morse <james.morse@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Signed-off-by: Jungseok Lee <jungseoklee85@gmail.com>
> ---
> arch/arm64/kernel/traps.c | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/arch/arm64/kernel/traps.c b/arch/arm64/kernel/traps.c
> index f93aae5..4ddb928 100644
> --- a/arch/arm64/kernel/traps.c
> +++ b/arch/arm64/kernel/traps.c
> @@ -103,12 +103,13 @@ static void dump_mem(const char *lvl, const char *str, unsigned long bottom,
> set_fs(fs);
> }
>
> -static void dump_backtrace_entry(unsigned long where, unsigned long stack)
> +static void dump_backtrace_entry(unsigned long where)
> {
> + /*
> + * The highest stack frame of a swapper process stores PC in a form
> + * of physical address, but this case is not handled.
> + */
> print_ip_sym(where);
> - if (in_exception_text(where))
> - dump_mem("", "Exception stack", stack,
> - stack + sizeof(struct pt_regs), false);
> }
>
> static void dump_instr(const char *lvl, struct pt_regs *regs)
> @@ -172,12 +173,17 @@ static void dump_backtrace(struct pt_regs *regs, struct task_struct *tsk)
> pr_emerg("Call trace:\n");
> while (1) {
> unsigned long where = frame.pc;
> + unsigned long stack;
> int ret;
>
> + dump_backtrace_entry(where);
> ret = unwind_frame(&frame);
> if (ret < 0)
> break;
> - dump_backtrace_entry(where, frame.sp);
> + stack = frame.sp;
> + if (in_exception_text(where))
> + dump_mem("", "Exception stack", stack,
> + stack + sizeof(struct pt_regs), false);
AFAICT, the original code is all based on unwind_backtrace in
arch/arm/kernel/unwind.c. Does that need updating too (as a separate patch)?
Will
next prev parent reply other threads:[~2015-10-15 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 13:21 [PATCH] arm64: Synchonise dump_backtrace() with perf callchain Jungseok Lee
2015-10-15 13:21 ` Jungseok Lee
2015-10-15 17:26 ` Will Deacon [this message]
2015-10-15 17:26 ` Will Deacon
2015-10-16 12:52 ` Jungseok Lee
2015-10-16 12:52 ` Jungseok Lee
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=20151015172600.GD19202@arm.com \
--to=will.deacon@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.