From: Jason Wessel <jason.wessel@windriver.com>
To: <linux-kernel@vger.kernel.org>
Cc: <kgdb-bugreport@lists.sourceforge.net>,
<masami.hiramatsu.pt@hitachi.com>, <tim.bird@am.sony.com>
Subject: [PATCH 0/2] Fix KGDB to work with CONFIG_DEBUG_RODATA using kprobe API
Date: Wed, 21 Mar 2012 12:55:34 -0500 [thread overview]
Message-ID: <1332352536-29186-1-git-send-email-jason.wessel@windriver.com> (raw)
The inability to use software breakpoints on a kernel built with
CONFIG_DEBUG_RODATA has been a problem for quite a few years. The
kprobes API has been working around this limitation for a long
time. This patch set changes the debug_core to use the kprobe
breakpoint API directly for a kernel compiled with CONFIG_DEBUG_RODATA.
Comments are welcome of course.
Thanks,
Jason.
---
Jason Wessel (2):
kgdb,debug_core: pass the breakpoint struct instead of address and memory
kgdb,debug_core,kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints
drivers/misc/kgdbts.c | 13 ------
include/linux/kgdb.h | 7 ++-
kernel/debug/debug_core.c | 93 ++++++++++++++++++++++++++++++--------------
3 files changed, 67 insertions(+), 46 deletions(-)
next reply other threads:[~2012-03-21 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 17:55 Jason Wessel [this message]
2012-03-21 17:55 ` [PATCH 1/2] kgdb,debug_core: pass the breakpoint struct instead of address and memory Jason Wessel
2012-03-21 17:55 ` [PATCH 2/2] kgdb,debug_core,kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints Jason Wessel
2012-03-22 2:53 ` Masami Hiramatsu
2012-03-22 11:57 ` Jason Wessel
2012-03-23 14:08 ` Masami Hiramatsu
2012-03-23 14:38 ` Jason Wessel
2012-03-26 9:46 ` Masami Hiramatsu
2012-03-26 16:39 ` Jason Wessel
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=1332352536-29186-1-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=tim.bird@am.sony.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
all inboxes | Powered by JetHome®