public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Luca Barbieri <luca.barbieri@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Zachary Amsden <zamsden@redhat.com>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	ming.m.lin@intel.com, sheng.yang@intel.com,
	Jes Sorensen <Jes.Sorensen@redhat.com>,
	KVM General <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>,
	Fr??d??ric Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: KVM usability
Date: Sun, 07 Mar 2010 20:16:26 +0200	[thread overview]
Message-ID: <4B93ED7A.6070204@redhat.com> (raw)
In-Reply-To: <ff13bc9a1003070714q3963a302ne37a57537423da57@mail.gmail.com>

On 03/07/2010 05:14 PM, Luca Barbieri wrote:
>> perf really is wonderful, but to be really competitive, and usable to more
>> developers, it needs to be in a graphical environment.  I want 'perf report'
>> output to start out collapsed and drill down by clicking on a tree widget.
>>   Clicking on a function name opens its definition.  'perf annotate' should
>> display annotations on my editor window, not in a pager.  I should be able
>> to check events on a list, not using 'perf list'.
>>
>> Is something like that suitable for tools/perf/?  I think you'll find the
>> intersection of kernel developers and GUI developers to be fairly small.
>>      
> The latest versions of Gnome Sysprof use perf and provide a GTK+ tree
> interface for the profiling output.
>
> However, they are not configurable at all and don't support anything
> but call graph profiling, unless they added more features very
> recently.
> It would be nice to extend sysprof into a more capable tool, and one
> that can read perf output files and do so when launched from the
> command line.
>    

Looks like a step in the right direction.  I don't think this belong in 
tools/, though.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2010-03-07 18:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B87A6BF.3090301@redhat.com>
     [not found] ` <20100226111734.GE7463@elte.hu>
     [not found]   ` <4B8813F2.8090208@redhat.com>
     [not found]     ` <20100227105643.GA17425@elte.hu>
     [not found]       ` <4B893B2B.40301@redhat.com>
     [not found]         ` <20100227172546.GA31472@elte.hu>
     [not found]           ` <4B8BEFC7.2040000@redhat.com>
     [not found]             ` <20100301174106.GB2362@ghostprotocols.net>
     [not found]               ` <4B8C0778.8050908@redhat.com>
     [not found]                 ` <20100301205620.GA26151@elte.hu>
2010-03-02 10:30                   ` KVM usability Ingo Molnar
2010-03-07  9:35                     ` Avi Kivity
2010-03-07  9:56                       ` Pekka Enberg
2010-03-07 10:11                         ` Avi Kivity
2010-03-07 18:42                         ` Ingo Molnar
2010-03-07 15:14                       ` Luca Barbieri
2010-03-07 18:16                         ` Avi Kivity [this message]
2010-03-07 18:01                       ` Arnaldo Carvalho de Melo
2010-03-07 18:15                         ` Avi Kivity
2010-03-07 18:53                           ` Arnaldo Carvalho de Melo
2010-03-07 19:05                             ` Avi Kivity

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=4B93ED7A.6070204@redhat.com \
    --to=avi@redhat.com \
    --cc=Jes.Sorensen@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=arjan@infradead.org \
    --cc=fweisbec@gmail.com \
    --cc=gleb@redhat.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.barbieri@gmail.com \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=sheng.yang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=yanmin_zhang@linux.intel.com \
    --cc=zamsden@redhat.com \
    /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