From: Xiongwei Song <sxwjean@me.com>
To: mpe@ellerman.id.au, benh@kernel.crashing.org, paulus@samba.org,
christophe.leroy@csgroup.eu, npiggin@gmail.com,
ravi.bangoria@linux.ibm.com, mikey@neuling.org,
aneesh.kumar@linux.ibm.com, 0x7f454c46@gmail.com
Cc: Xiongwei Song <sxwjean@gmail.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 2/2] powerpc: Print esr register when hitting Program Interrupt
Date: Thu, 22 Apr 2021 23:10:22 +0800 [thread overview]
Message-ID: <20210422151022.17868-2-sxwjean@me.com> (raw)
In-Reply-To: <20210422151022.17868-1-sxwjean@me.com>
From: Xiongwei Song <sxwjean@gmail.com>
The esr register has the details of Program Interrupt on BookE/4xx cpus,
printing its value is helpful.
Signed-off-by: Xiongwei Song <sxwjean@gmail.com>
---
arch/powerpc/kernel/process.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/kernel/process.c b/arch/powerpc/kernel/process.c
index 5c3830837f3a..664aecf8ee2e 100644
--- a/arch/powerpc/kernel/process.c
+++ b/arch/powerpc/kernel/process.c
@@ -1459,6 +1459,7 @@ static bool interrupt_detail_printable(int trap)
case INTERRUPT_MACHINE_CHECK:
case INTERRUPT_DATA_STORAGE:
case INTERRUPT_ALIGNMENT:
+ case INTERRUPT_PROGRAM:
return true;
default:
return false;
--
2.17.1
next prev parent reply other threads:[~2021-04-22 15:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 15:10 [PATCH 1/2] powerpc: Make the code in __show_regs nice-looking Xiongwei Song
2021-04-22 15:10 ` Xiongwei Song [this message]
2021-04-22 15:29 ` [PATCH 2/2] powerpc: Print esr register when hitting Program Interrupt Christophe Leroy
2021-04-22 16:49 ` Christophe Leroy
2021-04-24 14:21 ` Xiongwei Song
2021-04-24 13:51 ` Xiongwei Song
2021-04-22 15:27 ` [PATCH 1/2] powerpc: Make the code in __show_regs nice-looking Christophe Leroy
2021-04-24 14:36 ` Xiongwei Song
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=20210422151022.17868-2-sxwjean@me.com \
--to=sxwjean@me.com \
--cc=0x7f454c46@gmail.com \
--cc=aneesh.kumar@linux.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=sxwjean@gmail.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