mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: <linux-kernel@vger.kernel.org>
Cc: <kgdb-bugreport@lists.sourceforge.net>
Subject: [PATCH 0/6] KGDB/KDB/KGDBTS various regression fixes for 2.6.x -> 3.4
Date: Thu, 29 Mar 2012 17:48:56 -0500	[thread overview]
Message-ID: <1333061342-10132-1-git-send-email-jason.wessel@windriver.com> (raw)

This is a set of accumulated regression fixes which will go to to
-stable once reviewed and merged to the mainline.

The break down looks likes this for >= kernel x.x

   3.4: Fix an an Smatch warning that appeared in the 3.4 merge window
   3.0: Fix kgdb 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 suite with SMP for all archs with HW single stepping

It is worth mentioning that fixing the kgdb test suite SMP problems
has shown there are some stability problems with SMP ARM kernels and
IPIs.  These problems have been there for as long as ARM has had SMP
support but there was no easy way to trigger the issue that causes a
hard lockup.  At some point I'll take a further look at this, but
anyone is free to run the tests now that they work. :-)

Cheers,
Jason.

---
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     |  177 +++++++++++++++++++++++++++++++++------------
 include/linux/kgdb.h      |    7 +-
 kernel/debug/debug_core.c |   53 ++++++--------
 kernel/debug/kdb/kdb_io.c |    2 +-
 5 files changed, 221 insertions(+), 78 deletions(-)

             reply	other threads:[~2012-03-29 22:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-29 22:48 Jason Wessel [this message]
2012-03-29 22:48 ` [PATCH 1/6] kdb: Fix smatch warning on dbg_io_ops->is_console Jason Wessel
2012-03-29 22:48 ` [PATCH 2/6] kgdbts: Fix kernel oops with CONFIG_DEBUG_RODATA Jason Wessel
2012-03-29 22:48 ` [PATCH 3/6] kgdbts: (1 of 2) fix single step awareness to work correctly with SMP Jason Wessel
2012-03-29 22:49 ` [PATCH 4/6] kgdbts: (2 " Jason Wessel
2012-03-29 22:49 ` [PATCH 5/6] kgdb,debug_core: pass the breakpoint struct instead of address and memory Jason Wessel
2012-03-29 22:49 ` [PATCH 6/6] x86,kgdb: Fix DEBUG_RODATA limitation using text_poke() 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=1333061342-10132-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 \
    /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®