This patchkit adds the ability to turn off callgraphs and time stamps
per event. This in term can reduce sampling overhead and the size of
the perf.data.

Changes since V1:
  - Break up V1 patches into three patches(parse option changes,
    partial time support and partial callgraph support).
  - Use strings 'fp,dwarf,lbr,no' to identify callchains
  - Add test case in parse-events.c

Changes since V2:
  - Rebase on 60cd37eb10

Changes since V3:
  - Replace OPT_CALLBACK_SET by current existing callback mechanism.
  - Using perf_evsel__set_sample_bit if possible
  - Change the expression "partial" to "per event"
  - Using global variable to indicate if 'time' is set per event.
    If 'time' is not set, enable it by default for perf record.

Changes since V4:
  - Fix issue of setting callgraph_set

Changes since V5:
  - per-event settings over global settings in general
  - support for event post configuration structure

Jiri Olsa (2):
  perf tools: Add support for event post configuration
  perf tools: Force period term to overload global settings

Kan Liang (4):
  perf,tools: introduce callgraph_set for callgraph option
  perf,tool: per-event time support
  perf,tool: per-event callgraph support
  perf,tests: Add tests to callgraph and time parse

 tools/perf/Documentation/perf-record.txt | 10 +++-
 tools/perf/builtin-record.c              |  9 ++-
 tools/perf/perf.h                        |  1 +
 tools/perf/tests/parse-events.c          | 40 ++++++++++++-
 tools/perf/util/evsel.c                  | 98 ++++++++++++++++++++++++++++++--
 tools/perf/util/evsel.h                  | 26 +++++++++
 tools/perf/util/parse-events.c           | 91 +++++++++++++++++++++++++----
 tools/perf/util/parse-events.h           |  3 +
 tools/perf/util/parse-events.l           |  3 +
 tools/perf/util/pmu.c                    |  3 +-
 10 files changed, 260 insertions(+), 24 deletions(-)

-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to