[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170918072602.GB11683@krava>
Date: Mon, 18 Sep 2017 09:26:02 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: yuzhoujian <ufo19890607@...il.com>
Cc: peterz@...radead.org, mingo@...hat.com,
alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
dsahern@...il.com, namhyung@...nel.org, milian.wolff@...b.com,
arnaldo.melo@...il.com, yuzhoujian@...ichuxing.com,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] perf script: Add script per-event-dump support
On Mon, Sep 18, 2017 at 01:55:18PM +0800, yuzhoujian wrote:
> Introduce a new option to print trace output to files named by the
> monitored events and update perf-script documentation accordingly.
>
> Shown below is output of perf script command with the newly introduced
> option.
>
> $perf record -e cycles -e context-switches -ag -- sleep 10
> $perf script --per-event-dump
> $ls /
> cycles.stacks context-switches.stacks
hum, how adding -e option to be consistent with record, like:
$ perf record -e cycles -e context-switches ...
$ perf script -e cycles
--- dumps only cycles to perf.data
$ perf report -e cycles
--- displays only cycles
thanks,
jirka
Powered by blists - more mailing lists