Messages in this thread | | | Date | Wed, 22 Apr 2015 11:37:51 -0300 | From | Arnaldo Carvalho de Melo <> | Subject | Re: [RFC 0/6] perf tools: Report event parsing errors |
| |
Em Wed, Apr 22, 2015 at 04:08:50PM +0200, Jiri Olsa escreveu: > On Mon, Apr 20, 2015 at 05:38:52PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Mon, Apr 20, 2015 at 10:15:39PM +0200, Jiri Olsa escreveu: > > > On Mon, Apr 20, 2015 at 05:09:36PM -0300, Arnaldo Carvalho de Melo wrote: > > > > Which is nice, wouldn't it be good to have it for the that as well, i.e. > > > > for your example "ev=" would be a valid, and shorter form of "even=" or > > > > "event=".
> > > hum, not sure I follow.. could you please explain in more details?
> > This would be considered valid:
> > $ ./perf record -e 'cpu/even=0x1/' ls > > event syntax error: 'cpu/even=0x1/' > > \___ unknown term > > valid terms: "event", "raw".
> > "even=" would be recognized as a shorter form of "event=", "evint=" > > would be invalid :-)
> hum I see.. seem to be touching the bison/flex core part, might not > be that easy I'll think about it.. ;-)
This is just a "nice to have" feature, that would make it consistent accross the tools, i.e. it works for long option processing, it would work for event parsing, etc, but I guess you can leave it for when there is a blizzard and you get stuck at home or something like that ;-)
- Arnaldo
| |