mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: akpm@linux-foundation.org, fweisbec@gmail.com,
	LKML <linux-kernel@vger.kernel.org>,
	Don Zickus <dzickus@redhat.com>
Subject: [PATCH 0/2] touch_nmi_watchdog semantic changes
Date: Tue,  4 Jan 2011 22:38:29 -0500	[thread overview]
Message-ID: <1294198711-15492-1-git-send-email-dzickus@redhat.com> (raw)

I was trying to change the semantics of how touch_nmi_watchdog worked
to cover a corner case where endless console writing would block the
watchdog from going off.

Ingo recommended that I add ratelimiting to the panic code to in case we
get a slew of locked up cpus, hence my first patch in the series.

Cheers,
Don

--
Crap forgot to cc lkml, sorry for the spam...


Don Zickus (2):
  panic:  ratelimit panic messages
  watchdog:  touch_nmi_watchdog should only touch local cpu not every
    one

 Documentation/kernel-parameters.txt |    6 ++++++
 kernel/panic.c                      |   30 ++++++++++++++++++++++++++++++
 kernel/watchdog.c                   |   17 +++++++++--------
 3 files changed, 45 insertions(+), 8 deletions(-)

-- 
1.7.3.4


             reply	other threads:[~2011-01-05  3:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05  3:38 Don Zickus [this message]
2011-01-05  3:38 ` [PATCH 1/2] panic: ratelimit panic messages Don Zickus
2011-01-05 13:21   ` Ingo Molnar
2011-01-05 14:00     ` Don Zickus
2011-01-05 22:51   ` Andrew Morton
2011-01-06  2:05     ` Don Zickus
2011-01-06  2:16       ` Andrew Morton
2011-01-15  8:29     ` Dave Young
2011-01-15 11:03       ` Dave Young
2011-01-05  3:38 ` [PATCH 2/2] watchdog: touch_nmi_watchdog should only touch local cpu not every one Don Zickus

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=1294198711-15492-1-git-send-email-dzickus@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --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

all inboxes | Powered by JetHome®