From: Anton Blanchard <anton@samba.org>
To: Soeren Sandmann <sandmann@daimi.au.dk>
Cc: John Levon <levon@movementarian.org>,
bert hubert <bert.hubert@netherlabs.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Announce: Sysprof 1.0 -- a sampling, systemwide Linux profiler
Date: Sun, 18 Sep 2005 10:25:50 +1000 [thread overview]
Message-ID: <20050918002550.GB17639@krispykreme> (raw)
In-Reply-To: <ye88xxvi9g3.fsf@zebra02.daimi.au.dk>
Hi,
> My motive is not to duplicate oprofile - I basically don't care about
> the kernel level mechanism as long as it can produce stack traces that
> the GUI can interprete and analyse. In fact, one of the first times I
> wrote about sysprof publicly [1], I said:
>
> It seems to me that since oprofile probably reports more and
> better data than my kernel module, we should try and get the
> graphical presentation from sysprof to present oprofile data.
>
> and I still think so, but it's a fairly substantial amount of work to
> get rid of 296 lines of code.
Looking at your kernel module it should be pretty easy to plug on top of
oprofile callgraph data. All the hard work of programming hardware
performance counters will then come for free. Cross platform support
will also come for free.
Anton
next prev parent reply other threads:[~2005-09-18 0:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 21:05 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
2005-09-17 23:03 ` Soeren Sandmann
2005-09-18 0:25 ` Anton Blanchard [this message]
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=20050918002550.GB17639@krispykreme \
--to=anton@samba.org \
--cc=bert.hubert@netherlabs.nl \
--cc=levon@movementarian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®