From: Albert Cahalan <albert@users.sf.net>
To: mikpe@csd.uu.se
Cc: Andrew Fleming <afleming@motorola.com>,
Segher Boessenkool <segher@koffie.nl>,
Albert Cahalan <albert@users.sourceforge.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
oprofile-list@lists.sourceforge.net,
linuxppc-dev@lists.linuxppc.org, o.oppitz@web.de,
linux-kernel@vger.kernel.org
Subject: Re: [patch] oprofile for ppc
Date: 11 Mar 2003 19:10:53 -0500 [thread overview]
Message-ID: <1047427855.5973.80.camel@cube> (raw)
In-Reply-To: <15982.29106.674299.704117@gargle.gargle.HOWL>
On Tue, 2003-03-11 at 18:30, mikpe@csd.uu.se wrote:
>>>>> Benjamin Herrenschmidt wrote:
>>>>>> Beware though that some G4s have a nasty bug that
>>>>>> prevents using the performance counter interrupt
>>>>>> (and the thermal interrupt as well).
...
> Is this bug restricted to 7400/7410 only, or does it
> affect the 750 (and relatives) and 604/604e too?
>
> I'm thinking about ppc support for my perfctr driver,
> and whether overflow interrupts are worth supporting
> or not given the errata.
604/604e doesn't even have performance monitoring AFAIK.
I've heard nothing to suggest that the 750 is affected.
I'll give you a hand; point me to the latest perfctr code
and explain how it is supposed to interact with oprofile.
next prev parent reply other threads:[~2003-03-12 0:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 9:29 [patch] oprofile for ppc Albert D. Cahalan
2003-03-07 10:13 ` Benjamin Herrenschmidt
2003-03-07 18:31 ` Albert Cahalan
2003-03-08 15:10 ` Benjamin Herrenschmidt
2003-03-08 19:30 ` Albert Cahalan
2003-03-08 21:41 ` Benjamin Herrenschmidt
2003-03-10 4:00 ` Segher Boessenkool
2003-03-10 3:50 ` Segher Boessenkool
2003-03-10 6:31 ` Albert Cahalan
2003-03-10 8:43 ` Benjamin Herrenschmidt
2003-03-11 2:14 ` Segher Boessenkool
2003-03-11 21:54 ` Andrew Fleming
2003-03-11 23:13 ` Albert Cahalan
2003-03-12 0:25 ` Andrew Fleming
2003-03-11 23:30 ` mikpe
2003-03-12 0:10 ` Albert Cahalan [this message]
2003-03-12 10:42 ` mikpe
2003-03-10 8:38 ` Benjamin Herrenschmidt
2003-03-20 21:32 ` Andy Fleming
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=1047427855.5973.80.camel@cube \
--to=albert@users.sf.net \
--cc=afleming@motorola.com \
--cc=albert@users.sourceforge.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mikpe@csd.uu.se \
--cc=o.oppitz@web.de \
--cc=oprofile-list@lists.sourceforge.net \
--cc=segher@koffie.nl \
/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.