From: Keith Owens <kaos@ocs.com.au>
To: mingo@elte.hu
Cc: Andrew Morton <andrewm@uow.edu.au>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] serial console vs NMI watchdog
Date: Sun, 11 Mar 2001 18:52:02 +1100 [thread overview]
Message-ID: <15829.984297122@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 11 Mar 2001 08:44:24 BST." <Pine.LNX.4.30.0103110841110.987-100000@elte.hu>
On Sun, 11 Mar 2001 08:44:24 +0100 (CET),
Ingo Molnar <mingo@elte.hu> wrote:
>Andrew,
>
>your patch looks too complex, and doesnt cover the case of the serial
>driver deadlocking. Why not add a "touch_nmi_watchdog_counter()" function
>that just changes last_irq_sums instead of adding locking? This way
>deadlocks will be caught in the serial code too. (because touch_nmi() will
>only "postpone" the NMI watchdog lockup event, not disable it.)
kdb has to completely disable the nmi counter while it is in control.
All interrupts are disabled, all but one cpus are spinning, the control
cpu does busy wait while it polls the input devices. With that model
there is no alternative to a complete disable.
next prev parent reply other threads:[~2001-03-11 7:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 14:21 [patch] serial console vs NMI watchdog Andrew Morton
2001-03-09 16:35 ` Ion Badulescu
2001-03-10 2:41 ` Andrew Morton
2001-03-09 22:23 ` Robert Read
2001-03-11 7:44 ` Ingo Molnar
2001-03-11 7:52 ` Keith Owens [this message]
2001-03-11 7:53 ` Ingo Molnar
2001-03-11 8:00 ` Keith Owens
2001-03-11 8:16 ` Andrew Morton
2001-03-11 9:01 ` [patch] nmi-watchdog-2.4.2-A1 Ingo Molnar
2001-03-11 10:08 ` Andrew Morton
2001-03-11 15:04 ` [patch] nmi-watchdog-2.4.2-A2 Ingo Molnar
2001-03-12 4:43 ` [patch] serial console vs NMI watchdog george anzinger
2001-03-12 5:52 ` Keith Owens
2001-03-12 8:27 ` george anzinger
2001-03-12 8:41 ` Keith Owens
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=15829.984297122@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--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).