public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Philip Mucci <mucci@cs.utk.edu>
To: linux-ia64@vger.kernel.org
Subject: Re: [Gelato-technical] RE: q-tools v0.2 released
Date: Tue, 07 Dec 2004 10:21:05 +0000	[thread overview]
Message-ID: <1102414865.3969.6.camel@muccislaptop.pdc.kth.se> (raw)

Hi Ken,

If you want an overall system profile, why not use oprofile? That's what
it's made for....tools like q-tools, hpctoolkit, psrun, vprof, and papi-
like tools are application tools...

Phil


On Mon, 2004-12-06 at 18:38 -0800, Chen, Kenneth W wrote:
> David Mosberger wrote on Monday, October 11, 2004 8:53 AM
> > I'm happy to announce that q-tools v0.2 has been released.  q-tools is
> > a collection of Linux performance analysis tools.  In particular, they
> > include q-syscollect and q-view, which can be thought of as being more
> > powerful than gprof, without its pain (no recompilation needed;
> > multi-threaded apps and shared libraries are supported;
> > kernel-execution can be profiled; any Itanium 2 PMU event can be
> > profiled, etc.).
> >
> 
> I'm craving for more, is there a q-merge kind of utility out there? i.e.,
> merge all the cpu .hist files into one to get an overall system profile.  I
> can do that right now by hand (cat cpu*.hist into one file and then generate
> corresponding .info file).  I hope someone already had such tool so I don't
> have to reinvent the wheel.
> 
> - Ken
> 
> 
> 
> _______________________________________________
> Gelato-technical mailing list
> Gelato-technical@gelato.unsw.edu.au
> https://www.gelato.unsw.edu.au/mailman/listinfo/gelato-technical


             reply	other threads:[~2004-12-07 10:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07 10:21 Philip Mucci [this message]
2004-12-07 16:32 ` [Gelato-technical] RE: q-tools v0.2 released David Mosberger

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=1102414865.3969.6.camel@muccislaptop.pdc.kth.se \
    --to=mucci@cs.utk.edu \
    --cc=linux-ia64@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