From: Andi Kleen <ak@suse.de>
To: Alexander Nyberg <alexn@telia.com>
Cc: Jan Beulich <JBeulich@novell.com>,
discuss@x86-64.org, linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [discuss] Re: [PATCH] adjust x86-64 watchdog tick calculation
Date: Thu, 12 May 2005 13:46:57 +0200 [thread overview]
Message-ID: <20050512114657.GD15690@wotan.suse.de> (raw)
In-Reply-To: <1115892008.918.7.camel@localhost.localdomain>
On Thu, May 12, 2005 at 12:00:08PM +0200, Alexander Nyberg wrote:
> tor 2005-05-12 klockan 10:27 +0200 skrev Jan Beulich:
> > (Note: Patch also attached because the inline version is certain to get
> > line wrapped.)
> >
> > Get the x86-64 watchdog tick calculation into a state where it can also
> > be used with nmi_hz other than 1Hz. Also do not turn on the watchdog by
> > default (as is already done on i386).
> >
>
> Why shouldn't the watchdog be turned on by default? It's an extremely
> useful debugging aid and it's not like it fires NMIs often (the nmi_hz
> is far from reality).
I agree, I definitely want to keep the watchdog enabled by default.
It is a invaluable debugging aid.
The only reason i386 has it turned off by default is that it did not
always work on some oudated hardware. Needs to be probably revisited
at some point too.
-Andi
next prev parent reply other threads:[~2005-05-12 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 8:27 [PATCH] adjust x86-64 watchdog tick calculation Jan Beulich
2005-05-12 10:00 ` Alexander Nyberg
2005-05-12 11:46 ` Andi Kleen [this message]
2005-05-12 14:29 ` [discuss] " Pavel Machek
2005-05-13 11:30 ` Andi Kleen
2005-05-13 19:52 ` Pavel Machek
2005-05-13 21:27 ` Lee Revell
2005-05-13 22:51 ` Pavel Machek
2005-05-13 22:56 ` Lee Revell
2005-05-13 23:21 ` Pavel Machek
2005-05-13 23:29 ` Dave Jones
2005-05-15 10:52 ` Andi Kleen
2005-05-15 10:36 ` Andi Kleen
2005-05-15 10:51 ` Pavel Machek
2005-05-15 10:54 ` 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=20050512114657.GD15690@wotan.suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=alexn@telia.com \
--cc=discuss@x86-64.org \
--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;
as well as URLs for NNTP newsgroup(s).