From: John Levon <levon@movementarian.org>
To: Soeren Sandmann <sandmann@daimi.au.dk>
Cc: bert hubert <bert.hubert@netherlabs.nl>, linux-kernel@vger.kernel.org
Subject: Re: Announce: Sysprof 1.0 -- a sampling, systemwide Linux profiler
Date: Sat, 17 Sep 2005 23:20:15 +0100 [thread overview]
Message-ID: <20050917222015.GA32019@trollied.org> (raw)
In-Reply-To: <ye8slw38i5g.fsf@horse06.daimi.au.dk>
On Sun, Sep 18, 2005 at 12:05:15AM +0200, Soeren Sandmann wrote:
> details. Oprofile may have improved since then, but when I started
> sysprof:
>
> - oprofile didn't work on anything but smp kernels
>
> - oprofile could not produce callgraph information without not only
> recompiling my kernel, but also patching the kernel
>
> - oprofile had a user interface that I simply didn't understand. As I
> remember it, I had to know about performance counters and how to
> translate those into binary masks
This is what you said first time I asked you, none of which explain why
you're continuing this duplication of effort, since *none* of the above
are true any more (and the first /never/ was).
> and you get data presented in a way that is just a whole lot more
> useful than the flat text files generated by oprofile.
Building a GUI around OProfile would have been welcome, but you've
chosen to re-implement the entire stack...
regards,
john
next prev parent reply other threads:[~2005-09-17 22:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 21:05 Announce: Sysprof 1.0 -- a sampling, systemwide Linux profiler Soeren Sandmann
2005-09-17 21:16 ` John Levon
2005-09-17 21:16 ` bert hubert
2005-09-17 22:05 ` Soeren Sandmann
2005-09-17 22:20 ` John Levon [this message]
2005-09-17 23:03 ` Soeren Sandmann
2005-09-18 0:25 ` Anton Blanchard
2005-09-17 23:28 ` Tomasz Torcz
2005-09-17 23:53 ` John Levon
2005-09-18 8:45 ` bert hubert
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=20050917222015.GA32019@trollied.org \
--to=levon@movementarian.org \
--cc=bert.hubert@netherlabs.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=sandmann@daimi.au.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.