From: Hiro Yoshioka <hyoshiok@miraclelinux.com>
To: rddunlap@osdl.org
Cc: jamagallon@able.es, mikpe@user.it.uu.se,
perfctr-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Cc: hyoshiok@miraclelinux.com
Subject: Re: [Perfctr-devel] Re: perfctr-2.5.0 released
Date: Mon, 17 Mar 2003 01:47:36 +0900 [thread overview]
Message-ID: <20030317014736O.hyoshiok@miraclelinux.com> (raw)
In-Reply-To: <33207.4.64.238.61.1047616615.squirrel@www.osdl.org>
Hi,
We have made a memory profiling tool based on the perfctr 2.5.0.
http://downloads.sourceforge.jp/hardmeter/2646/hardmeter-030314.tar.gz
The tool (hardmeter) is
1) patch to perfctr 2.5.0
2) ebs (PEBS (Precise Event Based Sampling) memory profiling tool)
3) API
Thanks,
Hiro
> >
> > On 03.11, Mikael Pettersson wrote:
> >> Version 2.5.0 of perfctr, the Linux/x86 performance
> >> monitoring counters driver, is now available at the usual
> >> place: http://www.csd.uu.se/~mikpe/linux/perfctr/
> >>
> >
> > Perhaps this has been asked for a million times, but I'm new to
> > perfctrs...
> > Is there any tool available to profile a program based on this ?
> > I have seen perfex, but that gives total counts. I would like something like
> > gprof... We are now optimizing some software and I would like to make my
> > colleagues leave Windows (they use Intel's VTune) and go to Linux.
> > Or at least compare the same kind of things between VTune on win and
> > 'something' in Linux that also uses the counters. They don't seem to trust
> > gprof. And, looking at the results, I'm beginning to untrust VTune...
>
> I hope that Mikael knows of some native Linux tools for this.
> However, Intel did announce Vtune for Linux recently (might still be
> in beta test), and there was a SuSE patch for it posted at
> kernelnewbies.org also. See:
>
> http://www.linuxhardware.org/comments.pl?sid=364&cid=530
> http://www.linuxhardware.org/articles/03/01/17/1633229.shtml
> http://kernelnewbies.org/kernels/SuSE81/SOURCES/patches.i386/50_vtune-ia32
> (warning: this is for 2.4.19)
>
> or google for "+vtune +linux".
>
> ~Randy
next prev parent reply other threads:[~2003-03-16 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 0:02 perfctr-2.5.0 released Mikael Pettersson
2003-03-14 1:25 ` J.A. Magallon
2003-03-14 4:36 ` Randy.Dunlap
2003-03-16 16:47 ` Hiro Yoshioka [this message]
2003-03-14 9:10 ` [Perfctr-devel] " Nils Smeds
2003-03-14 15:01 ` William Cohen
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=20030317014736O.hyoshiok@miraclelinux.com \
--to=hyoshiok@miraclelinux.com \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=rddunlap@osdl.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