From: Arjan van de Ven <arjan@infradead.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, sandmann@redhat.com,
tglx@tglx.de, hpa@zytor.com
Subject: Re: [PATCH] x86: add the debugfs interface for the sysprof tool
Date: Wed, 20 Feb 2008 14:36:54 -0800 [thread overview]
Message-ID: <20080220143654.20ae7bea@laptopd505.fenrus.org> (raw)
In-Reply-To: <1203543869.6243.106.camel@lappy>
On Wed, 20 Feb 2008 22:44:29 +0100
Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
>
> On Wed, 2008-02-20 at 13:07 -0800, Arjan van de Ven wrote:
> > On Wed, 20 Feb 2008 21:58:42 +0100
> > Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:
> >
> > >
> > > On Wed, 2008-02-20 at 11:26 -0800, Arjan van de Ven wrote:
> > >
> > > > 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 guess we have to agree to disagree here. Its plain useless from
> > > my POV.
> >
> > that's fine. Different tools for different people. sysprof isn't
> > aimed at kernel developers.
>
> That was speaking from userland days.
>
> But you forgot the more important points about API and wild-growth of
> duplicate interfaces.
yes there's multiple interfaces. There are multiple interfaces *today*.
Oprofile/perfmon2 are very focused on CPU events and have complex interfaces,
sysprof has a much more simple interface (and yes, very specific to syspref)
that just focuses on samples.
Sadly, I think there's use for both, and forcing both into the same straightjacket is a mistake imo.
--
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-02-20 22:37 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 20:37 Arjan van de Ven
2008-02-20 9:10 ` Ingo Molnar
2008-02-26 4:13 ` Anton Blanchard
2008-02-26 8:57 ` Ingo Molnar
2008-02-20 18:16 ` Peter Zijlstra
2008-02-20 18:39 ` Arjan van de Ven
2008-02-20 18:53 ` Peter Zijlstra
2008-02-20 18:58 ` Peter Zijlstra
2008-02-26 5:03 ` Anton Blanchard
2008-02-20 19:26 ` Arjan van de Ven
2008-02-20 20:58 ` Peter Zijlstra
2008-02-20 21:07 ` Arjan van de Ven
2008-02-20 21:44 ` Peter Zijlstra
2008-02-20 22:36 ` Arjan van de Ven [this message]
2008-02-23 8:11 ` Andrew Morton
2008-02-23 11:37 ` Ingo Molnar
2008-02-23 13:53 ` John Levon
2008-02-23 15:50 ` Ingo Molnar
2008-02-23 20:15 ` Soeren Sandmann
2008-02-23 20:42 ` Andrew Morton
2008-02-26 5:13 ` Anton Blanchard
2008-02-26 9:02 ` Ingo Molnar
2008-02-26 17:29 ` Andrew Morton
2008-02-27 14:05 ` Anton Blanchard
2008-02-24 13:10 ` Theodore Tso
2008-02-24 13:44 ` Ingo Molnar
2008-02-24 14:33 ` Ingo Molnar
2008-02-24 16:32 ` John Levon
2008-02-24 18:19 ` Theodore Tso
2008-02-23 18:40 ` Andrew Morton
2008-02-23 11:51 ` Pekka Enberg
2008-02-23 12:22 ` Ingo Molnar
2008-02-23 12:29 ` Pekka Enberg
2008-02-23 18:46 ` Andrew Morton
2008-02-24 2:49 ` Pekka Enberg
2008-02-24 3:12 ` Nicholas Miell
2008-02-26 6:27 ` Pekka Enberg
2008-02-26 6:48 ` Pekka Enberg
2008-02-26 8:55 ` Ingo Molnar
2008-02-23 14:54 ` Pekka Enberg
2008-02-23 19:01 ` Andrew Morton
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=20080220143654.20ae7bea@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sandmann@redhat.com \
--cc=tglx@tglx.de \
/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
Powered by JetHome