mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@colin2.muc.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Export touch_nmi_watchdog
Date: 5 Aug 2003 23:14:16 +0200	[thread overview]
Date: Tue, 5 Aug 2003 23:14:16 +0200	[thread overview]
Message-ID: <20030805211416.GD31598@colin2.muc.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0308051402300.2835-100000@home.osdl.org>

> Otherwise this will just keep on expanding. 

It does expand on i386 exactly because the watchdog is disabled by default.

Looks like a mistake to me. It should be on because having usable backtraces
on a deadlock/hang is useful enough that it outweights any other possible
disadvantages. That's especially true for kernels out there at user's boxes,
not just special debugging kernels run by developers.

[if there should be any hardware where it doesn't work it should be blacklisted
there]

-Andi


  parent reply	other threads:[~2003-08-05 21:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 19:29 Andi Kleen
2003-08-05 19:38 ` Andrew Morton
2003-08-05 20:08   ` Andi Kleen
2003-08-05 20:20     ` Arjan van de Ven
2003-08-05 20:25       ` Linus Torvalds
2003-08-05 20:31         ` Arjan van de Ven
2003-08-05 21:07           ` Linus Torvalds
2003-08-05 21:05             ` Tim Hockin
2003-08-05 21:14             ` Andi Kleen [this message]
2003-08-05 21:15               ` Arjan van de Ven
2003-08-05 21:19                 ` Andi Kleen
2003-08-05 22:14               ` Linus Torvalds
2003-08-06  0:07                 ` Andi Kleen
2003-08-06 11:06                   ` Ingo Oeser
2003-08-06 15:31                     ` Linus Torvalds
2003-08-05 20:45         ` Andi Kleen
2003-08-05 21:11       ` Andi Kleen

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=20030805211416.GD31598@colin2.muc.de \
    --to=ak@colin2.muc.de \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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®