Date: Sat, 17 Sep 2005 23:20:15 +0100
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
Message-ID: <20050917222015.GA32019@trollied.org>
References: <ye8br2r9zi7.fsf@horse06.daimi.au.dk> <20050917211656.GA27448@outpost.ds9a.nl> <ye8slw38i5g.fsf@horse06.daimi.au.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ye8slw38i5g.fsf@horse06.daimi.au.dk>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1201
Lines: 31

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/