From: Albert Cahalan <albert@users.sf.net>
To: mikpe@user.it.uu.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: perfctr-2.4.6 released
Date: 02 Mar 2003 13:13:40 -0500 [thread overview]
Message-ID: <1046628821.1111.354.camel@cube> (raw)
Mikael Pettersson writes:
> perfctr-2.4.6 is now available at the usual place:
> http://www.csd.uu.se/~mikpe/linux/perfctr/
So, what is it? I figure it does profiling, but that
sure is vague. The SourceForge site is pretty empty too.
>From freshmeat.net and an ANNOUNCE-2.5.0-pre1 file, I'm
guessing you made some user-readable x86 registers be
per-process instead of system-wide, but maybe you've
done much more or less.
Does it use the oprofile interface? (why or why not?)
Does it use the IA-64 perfmon system call?
Does it support the Pentium-MMX in an old PC?
Does it support the PowerPC MPC7400 ("G4") in a Mac?
(if not, what would porting involve?)
Does it handle the kernel itself?
Does it handle stripped dynamic libraries?
Does it handle unmodified executables? (regular, -s, -g)
Does it work without root privileges?
Does it unmangle names for C++ code?
next reply other threads:[~2003-03-02 18:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-02 18:13 Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 23:33 perfctr-2.4.6 released Mikael Pettersson
2003-03-01 14:07 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=1046628821.1111.354.camel@cube \
--to=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox