linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: janboe.ye@gmail.com (ye janboe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: show_regs dump stack when ARM_UNWIND enable
Date: Tue, 20 Jul 2010 23:54:17 +0800	[thread overview]
Message-ID: <AANLkTimbxrdFeA513Y59OX6y9lwfh3OBjqerazKcwIXx@mail.gmail.com> (raw)
In-Reply-To: <1279640276.10002.35.camel@e102109-lin.cambridge.arm.com>

Yes. both are same.

Is it ok to remove backtrace.S if ARM_UNWIND is enable?

Catalin

Is it ok to merge this patch first and then try replace __bactrace in
next patch?

Janboe

2010/7/20 Catalin Marinas <catalin.marinas@arm.com>:
> On Tue, 2010-07-20 at 23:24 +0800, janboe wrote:
>> __backtrace is empty when ARM_UNWIND enable, so instead dump_stack
>>
>> Signed-off-by: janboe <janboe.ye@gmail.com>
>> ---
>> ?arch/arm/kernel/process.c | ? ?4 ++++
>> ?1 files changed, 4 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/arm/kernel/process.c b/arch/arm/kernel/process.c
>> index acf5e6f..e7ad878 100644
>> --- a/arch/arm/kernel/process.c
>> +++ b/arch/arm/kernel/process.c
>> @@ -271,7 +271,11 @@ void show_regs(struct pt_regs * regs)
>> ? ? ? printk("\n");
>> ? ? ? printk("Pid: %d, comm: %20s\n", task_pid_nr(current), current->comm);
>> ? ? ? __show_regs(regs);
>> +#ifdef CONFIG_ARM_UNWIND
>> + ? ? dump_stack();
>> +#else
>> ? ? ? __backtrace();
>> +#endif
>> ?}
>
> It looks like both dump_stack() and __backtrace() (with FRAME_POINTER)
> have pretty much the same semantics. Maybe we could define __backtrace()
> to just call dump_stack() when ARM_UNWIND.
>
> --
> Catalin
>
>

  reply	other threads:[~2010-07-20 15:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20 15:24 [PATCH] arm: show_regs dump stack when ARM_UNWIND enable janboe
2010-07-20 15:37 ` Catalin Marinas
2010-07-20 15:54   ` ye janboe [this message]
2010-07-21  9:21     ` Catalin Marinas
2010-07-21 17:24       ` Janboe Ye
2010-07-22  8:00         ` Russell King - ARM Linux
2010-08-10  3:27           ` ye janboe
2010-08-10 22:59             ` Russell King - ARM Linux

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=AANLkTimbxrdFeA513Y59OX6y9lwfh3OBjqerazKcwIXx@mail.gmail.com \
    --to=janboe.ye@gmail.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 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).