From: Soeren Sandmann <sandmann@daimi.au.dk>
To: John Levon <levon@movementarian.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, tglx@tglx.de, hpa@zytor.com
Subject: Re: [PATCH] x86: add the debugfs interface for the sysprof tool
Date: 23 Feb 2008 21:15:52 +0100 [thread overview]
Message-ID: <ye8ejb3e8ef.fsf@camel10.daimi.au.dk> (raw)
In-Reply-To: <20080223135335.GA28464@totally.trollied.org.uk>
John Levon <levon@movementarian.org> writes:
> Soren wrote sysprof when he tried an earlier version of oprofile and
> found it slightly non-obvious. Instead of doing any of these things:
This is not accurate. Sysprof started by me adding a hierarchical call
view to speedprof, a SIGPROF profiler which was basically a hack in
memprof.
Oprofile did not work on my system at the time (Red Hat 9, I believe),
and the website said that I had to apply a patch to the kernel and
recompile, so I didn't try it.
The hierarchical call view in speedprof worked out so well that I
wrote a simple kernel module to produce system-wide stacktraces, and
fed them into speedprof. Since speedprof was just a hack in memprof, I
wrote a new GUI, and sysprof was born.
It was only later I tried oprofile and found it not only much more
difficult to use, but also much less useful when I did get it to work.
Soren
next prev parent reply other threads:[~2008-02-23 20:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 20:37 Arjan van de Ven
2008-02-20 9:10 ` Ingo Molnar
2008-02-26 4:13 ` Anton Blanchard
2008-02-26 8:57 ` Ingo Molnar
2008-02-20 18:16 ` Peter Zijlstra
2008-02-20 18:39 ` Arjan van de Ven
2008-02-20 18:53 ` Peter Zijlstra
2008-02-20 18:58 ` Peter Zijlstra
2008-02-26 5:03 ` Anton Blanchard
2008-02-20 19:26 ` Arjan van de Ven
2008-02-20 20:58 ` Peter Zijlstra
2008-02-20 21:07 ` Arjan van de Ven
2008-02-20 21:44 ` Peter Zijlstra
2008-02-20 22:36 ` Arjan van de Ven
2008-02-23 8:11 ` Andrew Morton
2008-02-23 11:37 ` Ingo Molnar
2008-02-23 13:53 ` John Levon
2008-02-23 15:50 ` Ingo Molnar
2008-02-23 20:15 ` Soeren Sandmann [this message]
2008-02-23 20:42 ` Andrew Morton
2008-02-26 5:13 ` Anton Blanchard
2008-02-26 9:02 ` Ingo Molnar
2008-02-26 17:29 ` Andrew Morton
2008-02-27 14:05 ` Anton Blanchard
2008-02-24 13:10 ` Theodore Tso
2008-02-24 13:44 ` Ingo Molnar
2008-02-24 14:33 ` Ingo Molnar
2008-02-24 16:32 ` John Levon
2008-02-24 18:19 ` Theodore Tso
2008-02-23 18:40 ` Andrew Morton
2008-02-23 11:51 ` Pekka Enberg
2008-02-23 12:22 ` Ingo Molnar
2008-02-23 12:29 ` Pekka Enberg
2008-02-23 18:46 ` Andrew Morton
2008-02-24 2:49 ` Pekka Enberg
2008-02-24 3:12 ` Nicholas Miell
2008-02-26 6:27 ` Pekka Enberg
2008-02-26 6:48 ` Pekka Enberg
2008-02-26 8:55 ` Ingo Molnar
2008-02-23 14:54 ` Pekka Enberg
2008-02-23 19:01 ` Andrew Morton
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=ye8ejb3e8ef.fsf@camel10.daimi.au.dk \
--to=sandmann@daimi.au.dk \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=levon@movementarian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@tglx.de \
/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
Powered by JetHome