[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171009153906.GH2482@two.firstfloor.org>
Date: Mon, 9 Oct 2017 08:39:06 -0700
From: Andi Kleen <andi@...stfloor.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
Andi Kleen <andi@...stfloor.org>, Jiri Olsa <jolsa@...nel.org>,
Wang Nan <wangnan0@...wei.com>, linux-kernel@...r.kernel.org,
Andi Kleen <ak@...ux.intel.com>, He Kuang <hekuang@...wei.com>,
Alexei Starovoitov <ast@...com>
Subject: Re: [PATCH 2/2] perf, tools: Don't force MetricExprs to lower case
> > > > perf stat -e cpu/uops_executed.core/ ls
> > > > perf stat -e uops_executed.core ls
> > >
> > > Ok. If it works it's fine for me.
>
> well it works, but it means that bpf file cannot contains any directory
> part.. which im not sure is ok with bpf folks ;-) anyone?
One way that may work is to
- switch to a new proper syntax for bpf
(like bpf("filename")) that can be parsed properly
- handle simple cases like just that file name in the old syntax
in a pre processing pass of the scanner that converts it.
- users who specify multiple scripts or combine with other events
in the same -e line would need to change their syntax, but I assume that's
relatively rare.
-Andi
Powered by blists - more mailing lists