All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH][2.6.9-rc2-mm3] perfctr ppc32 preliminary interrupt support
Date: Mon, 27 Sep 2004 09:49:45 +1000	[thread overview]
Message-ID: <1096242585.4965.3.camel@gaston> (raw)
In-Reply-To: <200409262305.i8QN59b4012254@harpo.it.uu.se>


> Tested on an MPC7455 (G4-type chip). The patch applies cleanly
> to and compiles ok in 2.6.9-rc2-mm3, but 2.6.9-rc2-mm3 has
> other problems on PPC32 so I tested it with 2.6.9-rc2 vanilla.

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.

Check out the erratas, but it may be worth adding a cputable
feature bit entry to note which models have useable interrupt
and which don't.




  reply	other threads:[~2004-09-26 23:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 23:05 [PATCH][2.6.9-rc2-mm3] perfctr ppc32 preliminary interrupt support Mikael Pettersson
2004-09-26 23:49 ` Benjamin Herrenschmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-27  0:25 Mikael Pettersson
2004-09-27  0:36 ` Benjamin Herrenschmidt
2004-09-27 20:05 Albert Cahalan
2004-09-27 22:54 ` Benjamin Herrenschmidt
2004-09-29 11:48 Mikael Pettersson

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=1096242585.4965.3.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.