From: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, Michael Ellerman <mpe@ellerman.id.au>
Cc: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Balbir Singh <bsingharora@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
Douglas Miller <dougmill@linux.vnet.ibm.com>,
Frederic Barrat <fbarrat@linux.vnet.ibm.com>
Subject: [PATCH] xmon: Setup xmon debugger hooks when first break-point is set
Date: Mon, 26 Feb 2018 17:06:07 +0530 [thread overview]
Message-ID: <20180226113607.20321-1-vaibhav@linux.vnet.ibm.com> (raw)
Presently sysrq key for xmon('x') is registered during kernel init
irrespective of the value of kernel param 'xmon'. Thus xmon is enabled
even if 'xmon=off' is passed on the kernel command line. However this
doesn't enable the kernel debugger hooks needed for instruction or data
breakpoints. Thus when a break-point is hit with xmon=off a kernel oops
of the form below is reported:
Oops: Exception in kernel mode, sig: 5 [#1]
< snip >
Trace/breakpoint trap
To fix this the patch checks and enables debugger hooks when an
instruction or data break-point is set via xmon console. It also clears
all breakpoints when xmon is disabled via debugfs.
Signed-off-by: Vaibhav Jain <vaibhav@linux.vnet.ibm.com>
---
arch/powerpc/xmon/xmon.c | 34 +++++++++++++++++++++++++++++++++-
1 file changed, 33 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc/xmon/xmon.c b/arch/powerpc/xmon/xmon.c
index 82e1a3ee6e0f..3679f5417a7e 100644
--- a/arch/powerpc/xmon/xmon.c
+++ b/arch/powerpc/xmon/xmon.c
@@ -1295,6 +1295,7 @@ bpt_cmds(void)
switch (cmd) {
#ifndef CONFIG_PPC_8xx
static const char badaddr[] = "Only kernel addresses are permitted for breakpoints\n";
+ static const char warnxmon[] = "xmon: Enabling debugger hooks\n";
int mode;
case 'd': /* bd - hardware data breakpoint */
mode = 7;
@@ -1315,6 +1316,11 @@ bpt_cmds(void)
dabr.address &= ~HW_BRK_TYPE_DABR;
dabr.enabled = mode | BP_DABR;
}
+ /* Enable xmon hooks if needed */
+ if (!xmon_on) {
+ printf(warnxmon);
+ xmon_on = 1;
+ }
break;
case 'i': /* bi - hardware instr breakpoint */
@@ -1335,6 +1341,12 @@ bpt_cmds(void)
if (bp != NULL) {
bp->enabled |= BP_CIABR;
iabr = bp;
+
+ /* Enable xmon hooks if needed */
+ if (!xmon_on) {
+ printf(warnxmon);
+ xmon_on = 1;
+ }
}
break;
#endif
@@ -1399,8 +1411,15 @@ bpt_cmds(void)
if (!check_bp_loc(a))
break;
bp = new_breakpoint(a);
- if (bp != NULL)
+ if (bp != NULL) {
bp->enabled |= BP_TRAP;
+
+ /* Enable xmon hooks if needed */
+ if (!xmon_on) {
+ printf(warnxmon);
+ xmon_on = 1;
+ }
+ }
break;
}
}
@@ -3651,9 +3670,22 @@ device_initcall(setup_xmon_sysrq);
#ifdef CONFIG_DEBUG_FS
static int xmon_dbgfs_set(void *data, u64 val)
{
+ int i;
+
xmon_on = !!val;
xmon_init(xmon_on);
+ /* make sure all breakpoints removed when disabling */
+ if (!xmon_on) {
+ for (i = 0; i < NBPTS; ++i)
+ bpts[i].enabled = 0;
+ /* if anything set inform user that breakpoints are cleared */
+ if (iabr || dabr.enabled)
+ pr_info("xmon: All breakpoints cleared\n");
+
+ iabr = NULL;
+ dabr.enabled = 0;
+ }
return 0;
}
--
2.14.3
next reply other threads:[~2018-02-26 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 11:36 Vaibhav Jain [this message]
2018-02-27 0:26 ` [PATCH] xmon: Setup xmon debugger hooks when first break-point is set Balbir Singh
2018-03-01 3:00 ` 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=20180226113607.20321-1-vaibhav@linux.vnet.ibm.com \
--to=vaibhav@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=bsingharora@gmail.com \
--cc=dougmill@linux.vnet.ibm.com \
--cc=fbarrat@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@samba.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).