From: Avi Kivity <avi@redhat.com>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Ingo Molnar <mingo@elte.hu>, Zachary Amsden <zamsden@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 21:05:39 +0200 [thread overview]
Message-ID: <4B93F903.4030602@redhat.com> (raw)
In-Reply-To: <20100307185358.GF16539@ghostprotocols.net>
On 03/07/2010 08:53 PM, Arnaldo Carvalho de Melo wrote:
>>> Do you really think that more kernel developers would use perf more
>>> frequently if it had some GUI?
>>>
>> Not much. Is perf's target kernel developers exclusively? Who are
>> we writing this kernel for?
>>
> No, we aren't writing this tool only for kernel developers exclusively,
> but that wasn't my question, it was badly formulated, sorry, I shouldn't
> have included "kernel" in it :-\
>
In this case, I will reformulate my answer. Very much.
>> Even for kernel developers there are advantages in a GUI, namely
>> that features are easily discovered, the amount of information is
>> easily controlled, and in that you can interact (not redo everything
>> from scratch every time you want to change something). The
>> difference between a curses based tool and a true GUI are minimal
>> for this audience.
>>
> Ok, I agree with you about easier discoverability of features, path
> shortened from report to annotate to starting the editor right at the
> line where some event of interest happened,
Another path is browse some function, start profiling, see perf data
fill up in the margin. Or, jump to callers. etc. You need an
integrated browser for that (or an emacs perf mode).
> will try to keep the
> routines not much coupled with ncurses, but definetely ncurses will be
> the first step.
>
Great. ncurses is certainly much easier to experiment with and will
likely provide useful experience.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2010-03-07 19:06 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
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 [this message]
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=4B93F903.4030602@redhat.com \
--to=avi@redhat.com \
--cc=Jes.Sorensen@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--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=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