From: Mikael Pettersson <mikpe@csd.uu.se>
To: Andrew Morton <akpm@osdl.org>
Cc: eranian@hpl.hp.com, linux-kernel@vger.kernel.org,
perfmon@napali.hpl.hp.com, linux-ia64@vger.kernel.org,
perfctr-devel@lists.sourceforge.net
Subject: Re: [Perfctr-devel] Re: quick overview of the perfmon2 interface
Date: Tue, 20 Dec 2005 11:19:47 +0000 [thread overview]
Message-ID: <17319.59603.761669.480900@alkaid.it.uu.se> (raw)
In-Reply-To: <20051220025156.a86b418f.akpm@osdl.org>
Andrew Morton writes:
> > - All Itanium processors (Itanium, McKinley/Madison, Montecito)
> > - Intel EM64T/Xeon. Includes support for PEBS and HyperThreading (produced by Intel)
> > - Intel P4/Xeon (32-bit). Includes support for PEBS and HyperThreading
> > - Intel Pentium M and P6 processors
> > - AMD 64-bit Opteron
> > - preliminary support for IBM Power 5 (produced by IBM)
> > - preliminary support for MIPS R5000 (produced by Phil Mucci)
>
> Which achitectures does perfctr support? More, I think?
The sets are incomparable.
Intel P5 up to P4/Xeon/EM64T, though not P4's PEBS.
AMD K7 and K8.
X86 clones with performance counters (VIA C3 and Cyrix' P5-clones).
Any x86 with TSC. (Still useful for accurate time measurements.)
PPC32 (604 up to 74xx).
Any PPC32 with TB. (Still useful for accurate time measurements.)
POWER4/G5/POWER5 (done by David Gibson not me).
Preliminary ARM/XScale support is working but stalled due to
more pressing commitments and unresolved ARM platform issues.
(Some XScale/PXA drivers clobber the PMU registers for no good reason.)
UltraSPARC would be trivial to support, except (1) I don't have one,
and (2) they already have a primitive pre-historic perfctr facility.
/Mikael
next prev parent reply other threads:[~2005-12-20 11:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 11:31 quick overview of the perfmon2 interface Stephane Eranian
2005-12-20 10:51 ` Andrew Morton
2005-12-20 11:19 ` Mikael Pettersson [this message]
2005-12-20 18:05 ` Tony Luck
2005-12-20 18:16 ` [Perfctr-devel] " Stephane Eranian
2005-12-20 23:52 ` David Gibson
2005-12-22 11:56 ` Stephane Eranian
2005-12-22 12:05 ` Christoph Hellwig
2005-12-22 15:37 ` [Perfctr-devel] " William Cohen
2005-12-22 17:23 ` Christoph Hellwig
2005-12-22 18:17 ` William Cohen
2005-12-22 18:36 ` John Reiser
2005-12-22 18:48 ` [perfmon] " Stephane Eranian
2005-12-21 22:39 ` Truong, Dan
2005-12-22 13:31 ` Truong, Dan
2005-12-22 13:46 ` Andrew Morton
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=17319.59603.761669.480900@alkaid.it.uu.se \
--to=mikpe@csd.uu.se \
--cc=akpm@osdl.org \
--cc=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.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