From: "Bryan O'Sullivan" <bos@serpentine.com>
To: bert hubert <ahu@ds9a.nl>
Cc: Mikael.Pettersson@csd.uu.se, linux-kernel@vger.kernel.org
Subject: Re: perfctr questions
Date: Thu, 01 Jul 2004 15:19:54 -0700 [thread overview]
Message-ID: <1088720394.32000.26.camel@serpentine.internal.keyresearch.com> (raw)
In-Reply-To: <20040701220448.GA16515@outpost.ds9a.nl>
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
On Fri, 2004-07-02 at 00:04 +0200, bert hubert wrote:
> I'm trying to test your performance counters stuff, but I can't get it to do
> anything remotely useful! Probably just me.
No, it's just obscure.
You have three options for now. The first is to read the Intel or AMD
CPU performance counter docs, which I don't recommend, because that kind
of thing is never fun.
The second is to build a library called PAPI, which includes a command
called papiex that provides a less intimidating performance counter
interface. However, building PAPI with a not-quite-the-same version of
perfctr is a bit daunting, so I don't recommend that, either.
Your third option is to build a version of perfex that I've hacked on,
but not had time to finish up and submit to Mikael. I've attached it as
a tarball. This includes a man page that makes the usage less scary,
and it also accepts (gasp) textual arguments instead of hex strings.
I've tested it on P6, Pentium M and AMD64 chips.
<b
--
Bryan O'Sullivan
Software Tools
PathScale, Inc.
[-- Attachment #2: perfex.tar.bz2 --]
[-- Type: application/x-bzip-compressed-tar, Size: 10493 bytes --]
next prev parent reply other threads:[~2004-07-01 22:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-01 22:04 bert hubert
2004-07-01 22:19 ` Bryan O'Sullivan [this message]
2004-07-01 22:56 ` bert hubert
2004-07-01 23:26 ` bert hubert
2004-07-02 10:21 Mikael Pettersson
2004-07-02 11:04 ` bert hubert
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=1088720394.32000.26.camel@serpentine.internal.keyresearch.com \
--to=bos@serpentine.com \
--cc=Mikael.Pettersson@csd.uu.se \
--cc=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®