From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH][2.6.9-rc2-mm3] perfctr ppc32 preliminary interrupt support
Date: Mon, 27 Sep 2004 10:36:42 +1000 [thread overview]
Message-ID: <1096245402.18029.8.camel@gaston> (raw)
In-Reply-To: <200409270025.i8R0PaxN012405@harpo.it.uu.se>
On Mon, 2004-09-27 at 10:25, Mikael Pettersson wrote:
> On Mon, 27 Sep 2004 09:49:45 +1000, Benjamin Herrenschmidt wrote:
> > 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.
>
> Oh I'm very much aware of that erratum. That's why I never
> even tried implementing this while I only had a 750/G3.
> The error appears to affect all classic 750s, all 7400s,
> and early 7410s. Late 7410s and all 744x/745x are Ok.
> I don't know if IBM's recent 750s (GX/FX) have the error,
> but their 750CXs do.
Oh, interesting... I wasn't sure about the G3s, though iirc,
we discovered the error in the first place with MOL on an old G3
indeed...
Ben.
next prev parent reply other threads:[~2004-09-27 0:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 0:25 [PATCH][2.6.9-rc2-mm3] perfctr ppc32 preliminary interrupt support Mikael Pettersson
2004-09-27 0:36 ` Benjamin Herrenschmidt [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 11:48 Mikael Pettersson
2004-09-27 20:05 Albert Cahalan
2004-09-27 22:54 ` 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=1096245402.18029.8.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--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