From: Michael Ellerman <mpe@ellerman.id.au>
To: linuxppc-dev@ozlabs.org
Cc: tj@kernel.org, akpm@linux-foundation.org, mikey@neuling.org
Subject: [PATCH v2 3/7] powerpc/64: Add logical PVR to the dump stack arch description
Date: Fri, 18 Jan 2019 00:30:38 +1100 [thread overview]
Message-ID: <20190117133042.793-3-mpe@ellerman.id.au> (raw)
In-Reply-To: <20190117133042.793-1-mpe@ellerman.id.au>
If we detect a logical PVR add that to the dump stack arch
description, which is printed in case of an oops.
eg: Hardware name: ... lpvr:0xf000004
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
v2: new.
diff --git a/arch/powerpc/kernel/prom.c b/arch/powerpc/kernel/prom.c
index ea2c3498067d..38a90097469a 100644
--- a/arch/powerpc/kernel/prom.c
+++ b/arch/powerpc/kernel/prom.c
@@ -371,8 +371,10 @@ static int __init early_init_dt_scan_cpus(unsigned long node,
*/
if (!dt_cpu_ftrs_in_use()) {
prop = of_get_flat_dt_prop(node, "cpu-version", NULL);
- if (prop && (be32_to_cpup(prop) & 0xff000000) == 0x0f000000)
+ if (prop && (be32_to_cpup(prop) & 0xff000000) == 0x0f000000) {
identify_cpu(0, be32_to_cpup(prop));
+ dump_stack_add_arch_desc("lpvr:0x%04x", be32_to_cpup(prop));
+ }
check_cpu_feature_properties(node);
check_cpu_pa_features(node);
--
2.20.1
next prev parent reply other threads:[~2019-01-17 13:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 13:30 [PATCH v2 1/7] dump_stack: Support adding to the dump stack arch description Michael Ellerman
2019-01-17 13:30 ` [PATCH v2 2/7] powerpc: Add PVR & CPU name to " Michael Ellerman
2019-01-17 13:30 ` Michael Ellerman [this message]
2019-01-17 13:30 ` [PATCH v2 4/7] powerpc: Add device-tree model " Michael Ellerman
2019-01-17 13:30 ` [PATCH v2 5/7] powerpc: Add ppc_md.name " Michael Ellerman
2019-01-17 13:30 ` [PATCH v2 6/7] powerpc/powernv: Add opal details " Michael Ellerman
2019-01-17 13:30 ` [PATCH v2 7/7] powerpc/pseries: Add firmware " 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=20190117133042.793-3-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=tj@kernel.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).