linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: linux-kernel@vger.kernel.org
Cc: kgdb-bugreport@lists.sourceforge.net, mingo@elte.hu
Subject: [PATCH 0/3] V2 kgdb regression fixes for 2.6.33
Date: Wed, 27 Jan 2010 16:25:21 -0600	[thread overview]
Message-ID: <1264631124-4837-1-git-send-email-jason.wessel@windriver.com> (raw)

I would like to get acks from the respective parties to fix these
reported regressions against kgdb in 2.6.33.

The constraints for the hw breakpoint API is possibly was definitely a
dicey issue, but is hopefully resolved in this series.  Even without
the constraints patch it is possible to use hw breakpoints in the
kernel debugger in the same manner that has existed since 2.6.26 (only
kgdb gets to use hw breakpoints).

The regression are:
  * hw breakpoints no longer work on x86 after the perf API merge
  * softlockup watchdog can reboot the system while using the kernel debugger
    *** This has been in linux-next for several months waiting for acks

Dropped from the series was the clocksource patch, it was resolved
separately.

I collected all the patches which could go into the tip branch or the
kgdb for_linus branch at the following location depending on the
status of the discussion that ensues.

git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_igno

Thanks,
Jason.

---

The following changes since commit be8cde8b24c9dca1e54598690115eee5b1476519:
  Linus Torvalds (1):
        Merge git://git.kernel.org/.../jejb/scsi-rc-fixes-2.6

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_ingo

Jason Wessel (3):
      softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume
      x86,hw_breakpoint,kgdb: kgdb to use hw_breakpoint API
      perf,hw_breakpoint,kgdb: No mutex taken for kernel debugger

 arch/x86/kernel/hw_breakpoint.c |    5 +-
 arch/x86/kernel/kgdb.c          |  251 ++++++++++++++++++++++++++++++---------
 include/linux/hw_breakpoint.h   |    2 +
 include/linux/sched.h           |    4 +
 kernel/hw_breakpoint.c          |   52 +++++++--
 kernel/kgdb.c                   |    9 +-
 kernel/softlockup.c             |   15 +++
 7 files changed, 264 insertions(+), 74 deletions(-)

             reply	other threads:[~2010-01-27 22:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 22:25 Jason Wessel [this message]
2010-01-27 22:25 ` [PATCH 1/3] softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume Jason Wessel
2010-01-29  8:07   ` Ingo Molnar
2010-01-29 14:51     ` Jason Wessel
2010-02-01  5:53       ` Dongdong Deng
2010-02-01  6:05         ` Jason Wessel
2010-02-01  6:41           ` Dongdong Deng
2010-02-01  7:27   ` [tip:core/urgent] softlockup: Add " tip-bot for Jason Wessel
2010-01-27 22:25 ` [PATCH 2/3] x86,hw_breakpoint,kgdb: kgdb to use hw_breakpoint API Jason Wessel
2010-01-27 22:25 ` [PATCH 3/3] perf,hw_breakpoint,kgdb: No mutex taken for kernel debugger Jason Wessel
2010-01-28 17:33   ` Frederic Weisbecker
2010-01-28 17:49     ` [PATCH 3/3] perf,hw_breakpoint,kgdb: No mutex taken for kerneldebugger Jason Wessel
2010-01-28 20:09       ` Frederic Weisbecker
2010-01-28 20:38         ` [PATCH 3/3] perf,hw_breakpoint,kgdb: No mutex taken forkerneldebugger 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=1264631124-4837-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=mingo@elte.hu \
    /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).