From: David Laight <David.Laight@ACULAB.COM>
To: "'Matthew Wilcox (Oracle)'" <willy@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <keescook@chromium.org>, Marc Zyngier <maz@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] arm64: Show three registers per line
Date: Wed, 21 Apr 2021 08:31:32 +0000 [thread overview]
Message-ID: <c3ef59f1c06b42ecaa05a84beb7321b3@AcuMS.aculab.com> (raw)
In-Reply-To: <20210420172245.3679077-1-willy@infradead.org>
From: Matthew Wilcox
> Sent: 20 April 2021 18:23
>
> Displaying two registers per line takes 15 lines. That improves to just
> 10 lines if we display three registers per line, which reduces the amount
> of information lost when oopses are cut off. It stays within 80 columns
> and matches x86-64.
>
> Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> ---
> arch/arm64/kernel/process.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/arch/arm64/kernel/process.c b/arch/arm64/kernel/process.c
> index 6e60aa3b5ea9..aff5a2c12297 100644
> --- a/arch/arm64/kernel/process.c
> +++ b/arch/arm64/kernel/process.c
> @@ -294,13 +294,10 @@ void __show_regs(struct pt_regs *regs)
> i = top_reg;
>
> while (i >= 0) {
> - printk("x%-2d: %016llx ", i, regs->regs[i]);
> - i--;
> + printk("x%-2d: %016llx", i, regs->regs[i]);
>
> - if (i % 2 == 0) {
> - pr_cont("x%-2d: %016llx ", i, regs->regs[i]);
> - i--;
> - }
> + while (i-- % 3)
> + pr_cont(" x%-2d: %016llx", i, regs->regs[i]);
>
> pr_cont("\n");
> }
I think I'd avoid pr_cont() to avoid 'mishaps' during concurrent oops.
This probably needs something like:
for (; i >= 0; i -= 3) {
switch (i) {
case 0:
printk("x%-2d: %016llx\n", i, regs->regs[i]);
break;
case 1:
printk("x%-2d: %016llx x%-2d: %016llx\n",
i, regs->regs[i], i - 1, regs->regs[i - 1]);
break;
default:
printk("x%-2d: %016llx x%-2d: %016llx x%-2d: %016llx\n",
i, regs->regs[i], i - 1, regs->regs[i - 1],
i - 2, regs->regs[i - 2]);
continue;
}
break;
}
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2021-04-21 8:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 17:22 Matthew Wilcox (Oracle)
2021-04-20 18:57 ` Kees Cook
2021-04-21 8:31 ` David Laight [this message]
2021-04-22 10:35 ` Will Deacon
2021-04-23 17:11 ` Catalin Marinas
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=c3ef59f1c06b42ecaa05a84beb7321b3@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=catalin.marinas@arm.com \
--cc=keescook@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=peterz@infradead.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.org \
--cc=willy@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
Powered by JetHome