From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Albert Cahalan <albert@users.sourceforge.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
mikpe@csd.uu.se
Subject: Re: [PATCH][2.6.9-rc2-mm3] perfctr ppc32 preliminary interrupt support
Date: Tue, 28 Sep 2004 08:54:04 +1000 [thread overview]
Message-ID: <1096325643.1101.60.camel@gaston> (raw)
In-Reply-To: <1096315531.1296.21.camel@cube>
On Tue, 2004-09-28 at 06:05, Albert Cahalan wrote:
> Benjamin Herrenschmidt writes:
>
> > Be careful that some G4's have a bug which can cause a
> > perf monitor interrupt to crash your kernel :( Basically, the
> > problem is if any of TAU or PerfMon interrupt happens at the
> > same time as a DEC interrupt, some revs of the CPU can get
> > confused and lose the previous exception state.
>
> Instead of excluding all these CPUs, simply put the
> clock tick on the PerfMon interrupt. There's a bit-flip
> that'll go at about 4 kHz on a system with a 100 MHz bus.
> That should do. One need not change HZ; the interrupt
> can be ignored whenever the timebase hasn't advanced
> enough to require another clock tick.
True, we can use the perfmon instead of the DEC for those
Ben.
next prev parent reply other threads:[~2004-09-27 22:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 20:05 [PATCH][2.6.9-rc2-mm3] perfctr ppc32 preliminary interrupt support Albert Cahalan
2004-09-27 22:54 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 11:48 Mikael Pettersson
2004-09-27 0:25 Mikael Pettersson
2004-09-27 0:36 ` Benjamin Herrenschmidt
2004-09-26 23:05 Mikael Pettersson
2004-09-26 23:49 ` Benjamin Herrenschmidt
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=1096325643.1101.60.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=albert@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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