From: Avi Kivity <avi@redhat.com>
To: Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Mike Galbraith" <efault@gmx.de>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
"Paul Mackerras" <paulus@samba.org>,
"Clark Williams" <williams@redhat.com>,
"\"Luis Claudio R. Gonçalves\"" <lclaudio@redhat.com>
Subject: Re: [PATCH v2 5/5] perf report: Initial TUI using newt
Date: Fri, 12 Mar 2010 10:21:56 +0200 [thread overview]
Message-ID: <4B99F9A4.9010203@redhat.com> (raw)
In-Reply-To: <20100311232952.GF28421@ghostprotocols.net>
On 03/12/2010 01:29 AM, Arnaldo Carvalho de Melo wrote:
> Em Thu, Mar 11, 2010 at 08:12:44PM -0300, Arnaldo Carvalho de Melo escreveu:
>
>> From: Arnaldo Carvalho de Melo<acme@redhat.com>
>>
>> Newt has widespread availability and provides a rather simple API as can be
>> seen by the size of this patch.
>>
>> The work needed to support it will benefit other frontends too.
>>
>> In this initial patch it just checks if the output is a tty, if not it falls
>> back to the previous behaviour, also if newt-devel/libnewt-dev is not installed
>> the previous behaviour is maintaned.
>>
>> Pressing enter on a symbol will annotate it, ESC in the annotation window will
>> return to the report symbol list.
>>
> For those not so curious as to apply and try it out, here is a
> screenshot of it in action:
>
> http://tglx.de/~acme/perf-newt.png
>
>
Looks really useful!
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-03-12 8:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 23:12 [PATCH v2 1/5] perf symbols: Bump plt synthesizing warning debug level Arnaldo Carvalho de Melo
2010-03-11 23:12 ` [PATCH v2 2/5] perf top: Export get_window_dimensions Arnaldo Carvalho de Melo
2010-03-11 23:12 ` [PATCH v2 3/5] perf tools: Use eprintf for pr_{err,warning,info} too Arnaldo Carvalho de Melo
2010-03-11 23:12 ` [PATCH v2 4/5] perf tools: Add missing bytes printed in hist_entry__fprintf Arnaldo Carvalho de Melo
2010-03-11 23:12 ` [PATCH v2 5/5] perf report: Initial TUI using newt Arnaldo Carvalho de Melo
2010-03-11 23:29 ` Arnaldo Carvalho de Melo
2010-03-12 5:43 ` Frederic Weisbecker
2010-03-12 8:21 ` Avi Kivity [this message]
2010-03-12 6:48 ` Mike Galbraith
[not found] ` <1268377317.24910.1.camel@marge.simson.net>
2010-03-12 13:56 ` Arnaldo Carvalho de Melo
2010-03-12 9:45 ` Ingo Molnar
2010-03-12 9:55 ` Avi Kivity
2010-03-12 13:27 ` Arnaldo Carvalho de Melo
2010-03-12 13:25 ` Arnaldo Carvalho de Melo
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=4B99F9A4.9010203@redhat.com \
--to=avi@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=efault@gmx.de \
--cc=fweisbec@gmail.com \
--cc=lclaudio@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=williams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.