[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180601230100.GN30764@tassilo.jf.intel.com>
Date: Fri, 1 Jun 2018 16:01:00 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: Alexey Budankov <alexey.budankov@...ux.intel.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH v2]: perf record: enable arbitrary event names thru name=
modifier
On Thu, May 31, 2018 at 05:08:12PM +0300, Alexey Budankov wrote:
>
> Enable complex event names containing [.:=,] symbols to be encoded into Perf
> trace using name= modifier e.g. like this:
>
> perf record -e cpu/name=\'OFFCORE_RESPONSE:request=DEMAND_RFO:response=L3_HIT.SNOOP_HITM\',\
> period=0x3567e0,event=0x3c,cmask=0x1/Duk ./futex
>
> Below is how it looks like in the report output. Please note explicit escaped
> quoting at cmdline string in the header so that thestring can be directly reused
> for another collection in shell:
Patch looks good, but new syntax also needs to be documented in some manpage
(e.g. perf list)
-Andi
Powered by blists - more mailing lists