From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: David Ahern <dsahern@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 2/3] perf trace: Add option to analyze events in a file versus live
Date: Wed, 28 Aug 2013 10:31:10 -0300 [thread overview]
Message-ID: <20130828133110.GD31260@ghostprotocols.net> (raw)
In-Reply-To: <521DF691.7080706@gmail.com>
Em Wed, Aug 28, 2013 at 07:09:37AM -0600, David Ahern escreveu:
> On 8/28/13 7:02 AM, Arnaldo Carvalho de Melo wrote:
> >Em Mon, Aug 26, 2013 at 09:52:14PM -0600, David Ahern escreveu:
> >>Allows capture of raw_syscall:* events and analyzed at a later
> >>time.
> >>+-r
> >>+--replay
> >>+ Process events from a given perf data file.
> >Shouldn't this be just -i/--input, like for 'report', 'annotate', etc?
> uh, arguably. But -i == inherit per a prior patch. record (-i =
> inherit) / report (-i = input file) collision.
Perhaps --inherit is seldom used and can stay just as --inherit so that
we can use -i/--input to keep it consistent with report/annotate/etc?
- Arnaldo
next prev parent reply other threads:[~2013-08-28 13:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 3:52 [PATCH 0/3] perf trace enhancements David Ahern
2013-08-27 3:52 ` [PATCH 1/3] perf evlist: Add tracepoint lookup by name David Ahern
2013-08-27 3:52 ` [PATCH 2/3] perf trace: Add option to analyze events in a file versus live David Ahern
2013-08-28 13:02 ` Arnaldo Carvalho de Melo
2013-08-28 13:09 ` David Ahern
2013-08-28 13:31 ` Arnaldo Carvalho de Melo [this message]
2013-08-27 3:52 ` [PATCH 3/3] perf trace: Honor target pid / tid options when analyzing a file David Ahern
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=20130828133110.GD31260@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=adrian.hunter@intel.com \
--cc=dsahern@gmail.com \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.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.