From: Michael Ellerman <mpe@ellerman.id.au>
To: <linuxppc-dev@ozlabs.org>
Cc: <linux-kernel@vger.kernel.org>, Anton Blanchard <anton@samba.org>,
tj@kernel.org, Andrew Morton <akpm@osdl.org>
Subject: [PATCH 2/6] powerpc: Add cpu name to dump stack arch description
Date: Tue, 5 May 2015 21:12:13 +1000 [thread overview]
Message-ID: <1430824337-15339-2-git-send-email-mpe@ellerman.id.au> (raw)
In-Reply-To: <1430824337-15339-1-git-send-email-mpe@ellerman.id.au>
As soon as we know the name of the cpu we're on, add it to the dump
stack arch description, which is printed in case of an oops.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/kernel/cputable.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/cputable.c
index 60262fdf35ba..cf5e0c9b80cb 100644
--- a/arch/powerpc/kernel/cputable.c
+++ b/arch/powerpc/kernel/cputable.c
@@ -15,6 +15,7 @@
#include <linux/threads.h>
#include <linux/init.h>
#include <linux/export.h>
+#include <linux/printk.h>
#include <asm/oprofile_impl.h>
#include <asm/cputable.h>
@@ -2174,6 +2175,8 @@ static struct cpu_spec * __init setup_cpu_spec(unsigned long offset,
}
#endif /* CONFIG_PPC64 || CONFIG_BOOKE */
+ dump_stack_add_arch_desc(t->cpu_name);
+
return t;
}
--
2.1.0
next prev parent reply other threads:[~2015-05-05 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 11:12 [PATCH 1/6] dump_stack: Support adding to the dump stack arch description Michael Ellerman
2015-05-05 11:12 ` Michael Ellerman [this message]
2015-05-06 23:50 ` [PATCH 2/6] powerpc: Add cpu name to " Michael Neuling
2015-05-05 11:12 ` [PATCH 3/6] powerpc: Add device-tree model " Michael Ellerman
2015-05-05 11:12 ` [PATCH 4/6] powerpc: Add ppc_md.name " Michael Ellerman
2015-05-05 11:12 ` [PATCH 5/6] powerpc/powernv: Add opal details " Michael Ellerman
2015-05-05 11:12 ` [PATCH 6/6] powerpc/pseries: Add firmware " Michael Ellerman
2015-05-05 21:16 ` [PATCH 1/6] dump_stack: Support adding to the " Andrew Morton
2015-05-06 0:13 ` Michael Ellerman
2015-05-08 6:59 ` 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=1430824337-15339-2-git-send-email-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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).