From: Mikael Pettersson <mikpe@csd.uu.se>
To: mingo@redhat.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org,
macro@ds2.pg.gda.pl
Subject: Re: [PATCH] 2.4.1-ac UP-APIC updates
Date: Wed, 21 Feb 2001 01:36:45 +0100 (MET) [thread overview]
Message-ID: <200102210036.BAA02313@harpo.it.uu.se> (raw)
On Tue, 20 Feb 2001 16:00:53 -0500 (EST), Ingo Molnar wrote:
>my major gripe right now is that we still have bug reports that say that
>systems hang when using nmi_watchdog=1 and work if nmi_watchdog=0.
>Changing the NMI watchdog to be 1 Hz will make these bugreports "Linux
>hangs once a week" instead of a "Linux hangs after 1-2 hours", which is
>clearly hiding things and making debugging harder.
All reports I've seen have been for SMP kernels on MP machines using
the IO-APIC to drive the watchdog. Are you saying there are also cases
where UP boxes fail with nmi_watchdog non-zero? (My 1Hz change only
affected the local APIC-driven watchdog which MP boxes normally don't use.)
>(and driving kernel-profiling from the NMI interrupt is a short-term
>patch, so there is just no point in going to 1 Hz right now just to go
>back to 100 Hz a few days later.)
Another "constructive" use of the perfctrs. Ok, this I can see wants
a higher rate.
How far in the future is this? I'm concerned that the conflicting
uses of the perfctrs (watchdog, kernel profiling, my perfctr driver
for user-space performance measurements) is going to require some
low-level request/release API.
>the rest of the changes are excellent - it's only the 100 Hz NMI issue i
>have a problem with.
Ok.
Alan beat me to it for -ac20, so I'm not including a new patch now
with the 1Hz bit backed out. Ingo, I guess this means the kernel
profiling patch will have to "fix" the 1Hz thing by itself.
/Mikael
next reply other threads:[~2001-02-21 0:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-21 0:36 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-20 18:11 Mikael Pettersson
2001-02-20 18:46 ` Ingo Molnar
2001-02-20 20:55 ` Alan Cox
2001-02-20 21:00 ` Ingo Molnar
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=200102210036.BAA02313@harpo.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®