On Wed, 20 Feb 2008 19:53:42 +0100 Peter Zijlstra <[EMAIL PROTECTED]> wrote:
> > On Wed, 2008-02-20 at 10:39 -0800, Arjan van de Ven wrote: > > On Wed, 20 Feb 2008 19:16:15 +0100 > > Peter Zijlstra <[EMAIL PROTECTED]> wrote: > > > > > > > > On Tue, 2008-02-19 at 12:37 -0800, Arjan van de Ven wrote: > > > > From: Soren Sandmann <[EMAIL PROTECTED]> > > > > Subject: [PATCH] x86: add the debugfs interface for the sysprof > > > > tool > > > > > > > > The sysprof tool is a very easy to use GUI tool to find out > > > > where userspace is spending CPU time. See > > > > http://www.daimi.au.dk/~sandmann/sysprof/ > > > > for more information and screenshots on this tool. > > > > > > > > Sysprof needs a 200 line kernel module to do it's work, this > > > > module puts some simple profiling data into debugfs. > > > > > > What is the added value over oprofile? > > > > it actually works and is usable by humans ;) > > # sysprof > > (sysprof:12480): Gtk-WARNING **: cannot open display: > > -ENOX > > > what oprofile doesn't do is the nice userland hierarchy of where > > cpu time is spend. (and that is also what makes it mostly useless > > in practice) > > so why not fix oprofile callgraph output and build a GUI on top of > oprofile for those of us who really want RSI from mouse movement :-) feel free to reinvent a whole GUI just to avoid a 200 line kernel module. sysprof is here. it works. the gui is REALLY nice. I think it's the wrong tradeoff though... oprofile exists for how long? -- If you want to reach me at my work email, use [EMAIL PROTECTED] For development, discussion and tips for power savings, visit http://www.lesswatts.org -- 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/
