linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: paulmck@linux.vnet.ibm.com
Cc: linux-kernel@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net
Subject: [RFC PATCH 0/2] RCU stall handler for kernel debugger
Date: Mon,  9 Aug 2010 00:12:10 -0500	[thread overview]
Message-ID: <1281330732-17164-1-git-send-email-jason.wessel@windriver.com> (raw)

The purpose of this short series is to allow the kernel debugger to
reset the rcu stall timer when restarting the normal kernel execution
so as to prevent the rcu stall timer from issuing NMIs to print stack
traces that should be ignored because the kernel went away for a
while.

---
Jason Wessel (2):
      debug_core: move all watch dog syncs to a single function
      rcu,debug_core: allow the kernel debugger to reset the rcu stall timer

 include/linux/rcupdate.h  |    8 ++++++++
 kernel/debug/debug_core.c |   17 +++++++++++------
 kernel/rcutree.c          |    9 +++++++++
 3 files changed, 28 insertions(+), 6 deletions(-)

             reply	other threads:[~2010-08-09  5:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09  5:12 Jason Wessel [this message]
2010-08-09  5:12 ` [RFC PATCH 1/2] debug_core: move all watch dog syncs to a single function Jason Wessel
2010-08-09  5:12   ` [RFC PATCH 2/2] rcu,debug_core: allow the kernel debugger to reset the rcu stall timer Jason Wessel
2010-08-09 17:43     ` Paul E. McKenney
2010-08-09 18:26       ` Jason Wessel
2010-08-09 19:01         ` Paul E. McKenney
2010-08-11  4:01           ` Paul E. McKenney
2010-08-11 14:07             ` Jason Wessel
2010-08-11 16:32               ` Paul E. McKenney
2018-06-19 21:18     ` Paul E. McKenney
2018-06-20  9:55   ` [Kgdb-bugreport] [RFC PATCH 1/2] debug_core: move all watch dog syncs to a single function Daniel Thompson

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=1281330732-17164-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=paulmck@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).