[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160918145603.GN3078@tassilo.jf.intel.com>
Date: Sun, 18 Sep 2016 07:56:03 -0700
From: Andi Kleen <ak@...ux.intel.com>
To: "Wangnan (F)" <wangnan0@...wei.com>
Cc: Andi Kleen <andi@...stfloor.org>, acme@...nel.org,
jolsa@...nel.org, linux-kernel@...r.kernel.org,
sukadev@...ux.vnet.ibm.com
Subject: Re: [PATCH] perf, tools: Handle events including .c and .o
On Sun, Sep 18, 2016 at 06:20:04PM +0800, Wangnan (F) wrote:
>
>
> On 2016/9/18 9:02, Andi Kleen wrote:
> > From: Andi Kleen <ak@...ux.intel.com>
> >
> > This is a generic bug fix, but it helps with Sukadev's JSON event tree
> > where such events can happen.
> >
> > Any event inclduing a .c/.o/.bpf currently triggers BPF compilation or loading
> > and then an error. This can happen for some Intel JSON events, which cannot
> > be used.
> >
> > Fix the scanner to only match for .o or .c or .bpf at the end.
> > This will prevent loading multiple BPF scripts separated with comma,
> > but I assume this is acceptable.
> >
> > Cc: wangnan0@...wei.com
> > Cc: sukadev@...ux.vnet.ibm.com
> > Signed-off-by: Andi Kleen <ak@...ux.intel.com>
>
> I tested '.c' in middle of an event:
>
> # perf trace --event 'aaa.ccc'
> invalid or unsupported event: 'aaa.ccc'
> Run 'perf list' for a list of valid events
> ...
>
> It is not recongnized as a BPF source.
>
> So could you please provide an example to show how
> this potential bug breaks the parsing of new events?
This is with the upcoming JSON uncore events:
$ perf stat -e '{unc_p_clockticks,unc_p_power_state_occupancy.cores_c0}' -a -I 1000
ERROR: problems with path {unc_p_clockticks,unc_p_power_state_occupancy.c: No such file or directory
event syntax error: '{unc_p_clockticks,unc_p_power_state_occupancy.cores_c0}'
\___ Failed to load {unc_p_clockticks,unc_p_power_state_occupancy.c from source: Error when compiling BPF scriptlet
(add -v to see detail)
Run 'perf list' for a list of valid events
-Andi
Powered by blists - more mailing lists