From: Michael Ellerman <mpe@ellerman.id.au>
To: linuxppc-dev@ozlabs.org
Subject: [PATCH 2/2] powerpc: Show PAGE_SIZE in __die() output
Date: Tue, 8 Jan 2019 23:05:00 +1100 [thread overview]
Message-ID: <20190108120500.2547-2-mpe@ellerman.id.au> (raw)
In-Reply-To: <20190108120500.2547-1-mpe@ellerman.id.au>
The page size the kernel is built with is useful info when debugging a
crash, so add it to the output in __die().
Result looks like eg:
kernel BUG at drivers/misc/lkdtm/bugs.c:63!
Oops: Exception in kernel mode, sig: 5 [#1]
LE PAGE_SIZE=64K SMP NR_CPUS=2048 NUMA pSeries
Modules linked in: vmx_crypto kvm binfmt_misc ip_tables
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/kernel/traps.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/powerpc/kernel/traps.c b/arch/powerpc/kernel/traps.c
index 431a86d3f772..fc972e4eee5f 100644
--- a/arch/powerpc/kernel/traps.c
+++ b/arch/powerpc/kernel/traps.c
@@ -268,6 +268,18 @@ static int __die(const char *str, struct pt_regs *regs, long err)
else
seq_buf_puts(&s, "BE ");
+ seq_buf_puts(&s, "PAGE_SIZE=");
+ if (IS_ENABLED(CONFIG_PPC_4K_PAGES))
+ seq_buf_puts(&s, "4K ");
+ else if (IS_ENABLED(CONFIG_PPC_16K_PAGES))
+ seq_buf_puts(&s, "16K ");
+ else if (IS_ENABLED(CONFIG_PPC_64K_PAGES))
+ seq_buf_puts(&s, "64K ");
+ else if (IS_ENABLED(CONFIG_PPC_256K_PAGES))
+ seq_buf_puts(&s, "256K ");
+ else
+ BUILD_BUG_ON(1);
+
if (IS_ENABLED(CONFIG_PREEMPT))
seq_buf_puts(&s, "PREEMPT ");
--
2.20.1
next prev parent reply other threads:[~2019-01-08 12:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 12:04 [PATCH 1/2] powerpc: Use seq_buf to avoid pr_cont() in __die() Michael Ellerman
2019-01-08 12:05 ` Michael Ellerman [this message]
2019-01-08 12:21 ` [PATCH 2/2] powerpc: Show PAGE_SIZE in __die() output Christophe Leroy
2019-01-09 7:47 ` Christophe Leroy
2019-01-10 1:02 ` Michael Ellerman
2019-01-08 12:18 ` [PATCH 1/2] powerpc: Use seq_buf to avoid pr_cont() in __die() Christophe Leroy
2019-01-10 10:54 ` Michael Ellerman
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=20190108120500.2547-2-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.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).