From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: q-tools-0.0 released
Date: Sun, 07 Dec 2003 01:17:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107075994721581@msgid-missing> (raw)
[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 1136 bytes --]
OK, I guess I'm running very late with releasing it this week, but
better late than never: I finally got around to releasing a _snaphot_
of my profiling tools. They're very rough, but I think they might be
useful to a number of projects even in their current rough shape. I
have ideas and plans for many improvements but don't expect to find
time to work on q-tools for the next couple of weeks so either you'll
have to live with the current limitations or start sending
patches---either way is fine with me... ;-)
You can get q-tools from:
ftp://ftp.hpl.hp.com/pub/linux-ia64/q-tools-0.0.tar.gz
There is a README in there which should contain everything needed to
get you started (if not, complain and I'll fix it). Just as a teaser,
below is a picture you'd get when running the following commands on an
Itanium 2 machine with q-tools installed:
$ q-syscollect -k -t 10
$ q-dot kernel-cpu0.info | dot -Tps -Gcenter,rotate=90,size=10.75 | gv
Note that q-tools is all user-level stuff. There are no kernel
modules or patches of any sort required (apart from the normal perfmon
support in the 2.6 kernel).
Enjoy,
--david
[-- Attachment #2: call-graph for idle kernel --]
[-- Type: image/png, Size: 47745 bytes --]
next reply other threads:[~2003-12-07 1:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-07 1:17 David Mosberger [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 21:50 q-tools-0.0 released Grant Grundler
2004-02-05 22:28 ` Grant Grundler
2004-02-05 22:57 ` Stephane Eranian
2004-02-06 5:05 ` Grant Grundler
2004-02-06 7:26 ` Stephane Eranian
2004-02-06 12:24 ` Matthew Wilcox
2004-02-06 17:54 ` Al Stone
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=marc-linux-ia64-107075994721581@msgid-missing \
--to=davidm@napali.hpl.hp.com \
--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