[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131223130611.GB5076@gmail.com>
Date: Mon, 23 Dec 2013 14:06:11 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Paul Mackerras <paulus@...ba.org>,
Namhyung Kim <namhyung.kim@....com>,
LKML <linux-kernel@...r.kernel.org>,
Jiri Olsa <jolsa@...hat.com>, David Ahern <dsahern@...il.com>
Subject: Re: [PATCHSET 0/7] perf tools: A couple of TUI improvements (v2)
* Namhyung Kim <namhyung@...nel.org> wrote:
> > - it would be nice to have a hotkey to start/stop data collection on
> > demand, and another hotkey to reset the data. SysProf has this
> > feature, and it's a convenient workflow to have a separate 'data
> > collection' period (possibly done without any screen refresh, so
> > that data collection does not disturb the measured workload), and
> > a quiet 'look at all the data that is not being changed' period.
> > Especially with fast changing workloads the latter can be useful.
>
> I'm not sure I understood correctly. So do you want start/stop the
> 'record' part or 'report' part with hotkeys?
The 'record' part - a bit like SysProf.
> > - it would be nice if 'perf report' had a 'view raw trace' window as
> > well, with filtering. That would be roughly equivalent to the 'perf
> > report -D' output [but one line per trace entry, i.e. no hex dump
> > shown by default], all available within the TUI. With filtering
> > that would be a pretty good way to look at various details.
>
> Do you want something like 'perf script'? :)
Or perf trace, just in a TUI ;-)
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists