> - 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 all hasn't been true for a very long while.
> Contrast with sysprof, where you
> - insert the module
modprobe oprofile
> - hit the start button
opcontrol --start --vmlinux=/boot/vmlinux
> - do the thing you want to profile
> - hit the profile button
opcontrol --stop
opreport -l
> and you get data presented in a way that is just a whole lot more
> useful than the flat text files generated by oprofile.
Not *that* may be very true, and your GUI indeed looks very very promising.
Elsewhere you note regarding removing your sysprof.o code:
> and I still think so, but it's a fairly substantial amount of work to
> get rid of 296 lines of code.
You'll find this work orders of magnitude easier than convincing people that
we need yet another profiling system in the kernel.
So I urge you, keep the cool gui but adapt it to oprofile. I'm sure John
will be more than willing to work with you to make sure oprofile
supports/will support everything you need.
Ok?
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |