From: Anton Blanchard <anton@samba.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, sandmann@redhat.com, tglx@tglx.de,
hpa@zytor.com
Subject: Re: [PATCH] x86: add the debugfs interface for the sysprof tool
Date: Mon, 25 Feb 2008 22:13:49 -0600 [thread overview]
Message-ID: <20080226041349.GA17772@kryten> (raw)
In-Reply-To: <20080220091022.GB31424@elte.hu>
> > From: Soren Sandmann <sandmann@redhat.com>
> > 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.
>
> thanks, looks good to me - applied.
Woah slow down guys. Did I miss the review?
Yes it's a 200 line patch, but it's a 200 line x86 patch. Surely we
should apply some of the same rigour we did when we merged the oprofile
patch? Is it biarch safe? Will it run on powerpc, arm etc?
I'm still struggling to understand why we need this functionality at
all. Lets argue the ABI and not cloud it with a discussion about
userspace eye candy. What does this give you that is an improvement over
the oprofile kernel-user ABI?
Anton
next prev parent reply other threads:[~2008-02-26 4:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 20:37 [PATCH] x86: add the debugfs interface for the sysprof tool Arjan van de Ven
2008-02-20 9:10 ` Ingo Molnar
2008-02-26 4:13 ` Anton Blanchard [this message]
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
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=20080226041349.GA17772@kryten \
--to=anton@samba.org \
--cc=arjan@infradead.org \
--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