linux-kernel - Re: [PATCH 2/3] perf trace: Add option to analyze events in a file versus live

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Wed, 28 Aug 2013 10:31:10 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	David Ahern <dsahern@...il.com>
Cc:	linux-kernel@...r.kernel.org,
	Adrian Hunter <adrian.hunter@...el.com>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Stephane Eranian <eranian@...gle.com>
Subject: Re: [PATCH 2/3] perf trace: Add option to analyze events in a file
 versus live

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
--
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/