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 regression fixes for 2.6.33
Date: Thu, 28 Jan 2010 17:04:41 -0600 [thread overview]
Message-ID: <1264719883-7285-1-git-send-email-jason.wessel@windriver.com> (raw)
Linus, please pull the kgdb git tree fixes for 2.6.33-rc5
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus
Summary:
* Fix the kgdb regression in functionality caused by the new hw
breakpoint API changes in 2.6.33.
This leaves us with some cleanup in 2.6.34, but all the previous
functionality works again. In fact you can use hw breakpoints in user
space and the kernel at the same time now that the API is shared,
which is something that never previously worked.
Thanks,
Jason.
--
The following changes since commit be8cde8b24c9dca1e54598690115eee5b1476519:
Linus Torvalds (1):
Merge git://git.kernel.org/.../jejb/scsi-rc-fixes-2.6
--
Jason Wessel (2):
x86,hw_breakpoint,kgdb: kgdb to use hw_breakpoint API
perf,hw_breakpoint,kgdb: No mutex taken for kernel debugger
arch/x86/kernel/kgdb.c | 222 ++++++++++++++++++++++++++++++-----------
include/linux/hw_breakpoint.h | 2 +
kernel/hw_breakpoint.c | 52 ++++++++--
kernel/kgdb.c | 3 +
4 files changed, 212 insertions(+), 67 deletions(-)
next reply other threads:[~2010-01-28 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 23:04 Jason Wessel [this message]
2010-01-28 23:04 ` [PATCH 1/2] x86,hw_breakpoint,kgdb: kgdb to use hw_breakpoint API Jason Wessel
2010-01-28 23:04 ` [PATCH 2/2] perf,hw_breakpoint,kgdb: No mutex taken for kernel debugger Jason Wessel
2010-01-31 6:39 ` [tip:perf/urgent] perf, hw_breakpoint, kgdb: Do not take mutex " tip-bot for Jason Wessel
2010-01-31 6:39 ` [tip:perf/urgent] x86, hw_breakpoints, kgdb: Fix kgdb to use hw_breakpoint API tip-bot for 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=1264719883-7285-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
all inboxes | Powered by JetHome®