From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH 1/5] perf trace: Setup pager before running
Date: Fri, 5 Oct 2012 08:47:33 -0700 [thread overview]
Message-ID: <20121005154733.GA1738@ghostprotocols.net> (raw)
In-Reply-To: <1349413336-26936-1-git-send-email-namhyung@kernel.org>
Em Fri, Oct 05, 2012 at 02:02:12PM +0900, Namhyung Kim escreveu:
> From: Namhyung Kim <namhyung.kim@lge.com>
>
> Since perf trace emits lots of messages on terminal, it'd better using
> a pager.
Humm, I'm used to the strace behaviour, i.e. free flow of events, unsure
if using the pager in this specific case is right, perhaps it should be
optional.
In the TUI case, when we get to implement it there, I think that we can
go to/from pager mode, expanding callchains for pagefaults and other
events, for instance.
- Arnaldo
prev parent reply other threads:[~2012-10-05 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 5:02 [PATCH 1/5] perf trace: Setup pager before running Namhyung Kim
2012-10-05 5:02 ` [PATCH 2/5] perf trace: Validate target task/user/cpu argument Namhyung Kim
2012-10-09 17:19 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-10-05 5:02 ` [PATCH 3/5] perf trace: Explicitly enable system-wide mode if no option is given Namhyung Kim
2012-10-09 17:20 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-10-05 5:02 ` [PATCH 4/5] perf trace: Add -a switch for --all-cpus option Namhyung Kim
2012-10-05 5:02 ` [PATCH 5/5] perf trace: Add support for tracing workload given by command line Namhyung Kim
2012-10-09 17:21 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-10-05 15:47 ` Arnaldo Carvalho de Melo [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=20121005154733.GA1738@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
/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.