[PATCHv2 0/2] perf tool: parser generator for events parsing

[Jiri Olsa]

hi,
adding an event parser generator to handle the '-e' option data.
I strip this version of the event grouping enhancement, so it's
more straightforward. I'll send those patches later.

Attached patches:
  - 1/2 perf, tool: Add parser generator for events parsing
  - 2/2 perf, tool: Add more automated tests for event parsing

v2 changes:
  1/2 perf, tool: Add parser generator for events parsing
   - added a way to specify config[12] for raw events
   - added direct symbol -> raw mapping in parser itself
   - fixed modifier syntax to allow all correct precise
     values
   - added generated parser as part of the patch, however..
     flex and bison dont care about the linux kernel
     coding standard, checkpatch.pl complains quite a lot:

       total: 728 errors, 1316 warnings, 5379 lines checked

     after I tried cleanpatch scripts I've got:

       total: 664 errors, 1287 warnings, 5382 lines checked

     so I'm not sure it's worth to do that (the cleanup),
     considering it needs to be regenerated each time we change
     the parser grammar.
   - added 'event-parser' Makefile target to generate
     the parser out of the flex/bison sources

thanks,
jirka
---
 tools/perf/Makefile                  |   18 +
 tools/perf/builtin-test.c            |  276 +++++-
 tools/perf/util/parse-events-bison.c | 1743 ++++++++++++++++++++++++++
 tools/perf/util/parse-events-bison.h |   78 ++
 tools/perf/util/parse-events-flex.c  | 2256 ++++++++++++++++++++++++++++++++++
 tools/perf/util/parse-events-flex.h  |  317 +++++
 tools/perf/util/parse-events.c       |  475 +++-----
 tools/perf/util/parse-events.h       |   10 +
 tools/perf/util/parse-events.l       |  114 ++
 tools/perf/util/parse-events.y       |  131 ++
 10 files changed, 5094 insertions(+), 324 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/