mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: bert hubert <ahu@ds9a.nl>
To: "Bryan O'Sullivan" <bos@serpentine.com>
Cc: Mikael.Pettersson@csd.uu.se, linux-kernel@vger.kernel.org
Subject: Re: perfctr questions
Date: Fri, 2 Jul 2004 00:56:13 +0200	[thread overview]
Message-ID: <20040701225613.GA21173@outpost.ds9a.nl> (raw)
In-Reply-To: <1088720394.32000.26.camel@serpentine.internal.keyresearch.com>

Bryan,

Thanks for your quick reply!

On Thu, Jul 01, 2004 at 03:19:54PM -0700, Bryan O'Sullivan wrote:

> 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.

pepiex doesn't build for me, I was actually trying that already. It tries to
take over pthreads, which I think breaks. PAPI does look nice though.

> 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.

Ah, cool - seems to have bitrotted somewhat, perfctr_*_event_* appear no
longer to exist in perfctr 2.7.3.

In any case, your manpage inspired some command lines that at least appear
to generate numbers, thanks.

But we're obviously not there yet.

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

  reply	other threads:[~2004-07-01 22:56 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
2004-07-01 22:56   ` bert hubert [this message]
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=20040701225613.GA21173@outpost.ds9a.nl \
    --to=ahu@ds9a.nl \
    --cc=Mikael.Pettersson@csd.uu.se \
    --cc=bos@serpentine.com \
    --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®