From: Joe Perches <joe@perches.com>
To: Max Filippov <jcmvbkbc@gmail.com>, linux-xtensa@linux-xtensa.org
Cc: Chris Zankel <chris@zankel.net>,
linux-kernel@vger.kernel.org, Dmitry Safonov <dima@arista.com>,
Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH] xtensa: improve stack dumping
Date: Wed, 06 Nov 2019 14:33:55 -0800 [thread overview]
Message-ID: <a9e2f6b65d4c098ab027ea849120d3cf61858e67.camel@perches.com> (raw)
In-Reply-To: <20191106181617.1832-1-jcmvbkbc@gmail.com>
On Wed, 2019-11-06 at 10:16 -0800, Max Filippov wrote:
> Collect whole stack dump lines in a buffer and print the whole buffer
> when it's ready with pr_info instead of pr_cont. This makes stack dump
> lines consistent in SMP case and relies less on pr_cont/printk
> differences related to timestamps.
> Make size of stack dump configurable.
> Drop extra newline output in show_trace as its output format does not
> depend on CONFIG_KALLSYMS.
[]
> diff --git a/arch/xtensa/kernel/traps.c b/arch/xtensa/kernel/traps.c
[]
> @@ -512,10 +510,12 @@ void show_stack(struct task_struct *task, unsigned long *sp)
> for (i = 0; i < kstack_depth_to_print; i++) {
> if (kstack_end(sp))
> break;
> - pr_cont(" %08lx", *sp++);
> + sprintf(buf + (i % 8) * 9, " %08lx", *sp++);
> if (i % 8 == 7)
> - pr_cont("\n");
> + pr_info("%s\n", buf);
> }
> + if (i % 8)
> + pr_info("%s\n", buf);
Could this be done using hex_dump_to_buffer
by precalculating kstack_end ?
next prev parent reply other threads:[~2019-11-06 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 18:16 Max Filippov
2019-11-06 20:50 ` Dmitry Safonov
2019-11-06 22:00 ` Max Filippov
2019-11-06 22:18 ` Dmitry Safonov
2019-11-06 22:33 ` Joe Perches [this message]
2019-11-07 0:21 ` Max Filippov
2019-11-07 14:38 ` Petr Mladek
2019-11-07 14:45 ` Joe Perches
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=a9e2f6b65d4c098ab027ea849120d3cf61858e67.camel@perches.com \
--to=joe@perches.com \
--cc=chris@zankel.net \
--cc=dima@arista.com \
--cc=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=pmladek@suse.com \
/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®