[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1437035170-12911-1-git-send-email-kan.liang@intel.com>
Date: Thu, 16 Jul 2015 04:26:06 -0400
From: kan.liang@...el.com
To: acme@...nel.org, jolsa@...nel.org
Cc: namhyung@...nel.org, ak@...ux.intel.com,
linux-kernel@...r.kernel.org, Kan Liang <kan.liang@...el.com>
Subject: [PATCH RFC V4 0/4] per event callgrap and time support
From: Kan Liang <kan.liang@...el.com>
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 callgrap 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.
Kan Liang (4):
perf,tools: introduce callgraph_set for callgraph option
perf,tool: per-event time support
perf,tool: per-event callgrap support
perf,tests: Add tests to callgrap and time parse
tools/perf/Documentation/perf-record.txt | 8 ++++-
tools/perf/builtin-record.c | 13 ++++++--
tools/perf/builtin-trace.c | 1 +
tools/perf/perf.h | 1 +
tools/perf/tests/parse-events.c | 28 +++++++++++++++++
tools/perf/util/evsel.c | 54 ++++++++++++++++++++++++++++++--
tools/perf/util/parse-events.c | 29 +++++++++++++++++
tools/perf/util/parse-events.h | 5 +++
tools/perf/util/parse-events.l | 3 ++
tools/perf/util/pmu.c | 3 +-
10 files changed, 137 insertions(+), 8 deletions(-)
--
1.8.3.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists