From: Jason Wessel <jason.wessel@windriver.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>, <kgdb-bugreport@lists.sourceforge.net>
Subject: [GIT PULL] KGDB/KDB regression fixes for 3.4-rc2
Date: Mon, 2 Apr 2012 12:49:13 -0500 [thread overview]
Message-ID: <1333388953-32127-1-git-send-email-jason.wessel@windriver.com> (raw)
The following changes since commit 1ba0c1720eb0de2d0f3abf84c0b128d10af520d1:
kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint (2012-03-22 15:07:16 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git tags/for_linus-3.4-rc2
for you to fetch changes up to 3751d3e85cf693e10e2c47c03c8caa65e171099b:
x86,kgdb: Fix DEBUG_RODATA limitation using text_poke() (2012-03-29 17:41:25 -0500)
----------------------------------------------------------------
KGDB/KDB regression fixes
3.4: Fix an an Smatch warning that appeared in the 3.4 merge window
3.0: Fix kgdb test suite with SMP for all archs without HW single stepping
2.6.36: Fix kgdb sw breakpoints with CONFIG_DEBUG_RODATA=y limitations on x86
2.6.26: Fix oops on kgdb test suite with CONFIG_DEBUG_RODATA
Fix kgdb test suite with SMP for all archs with HW single stepping
----------------------------------------------------------------
Jason Wessel (6):
kdb: Fix smatch warning on dbg_io_ops->is_console
kgdbts: Fix kernel oops with CONFIG_DEBUG_RODATA
kgdbts: (1 of 2) fix single step awareness to work correctly with SMP
kgdbts: (2 of 2) fix single step awareness to work correctly with SMP
kgdb,debug_core: pass the breakpoint struct instead of address and memory
x86,kgdb: Fix DEBUG_RODATA limitation using text_poke()
arch/x86/kernel/kgdb.c | 60 +++++++++++++++++
drivers/misc/kgdbts.c | 160 ++++++++++++++++++++++++++++++++-------------
include/linux/kgdb.h | 7 +-
kernel/debug/debug_core.c | 53 +++++++--------
kernel/debug/kdb/kdb_io.c | 2 +-
5 files changed, 204 insertions(+), 78 deletions(-)
reply other threads:[~2012-04-02 17:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1333388953-32127-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=torvalds@linux-foundation.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).