From: Kan Liang <kan.liang@intel.com>
To: acme@kernel.org, jolsa@kernel.org
Cc: namhyung@kernel.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org, Kan Liang <kan.liang@intel.com>
Subject: [PATCH RFC V8 0/4] per event callgraph and time support
Date: Tue, 4 Aug 2015 04:30:18 -0400 [thread overview]
Message-ID: <1438677022-34296-1-git-send-email-kan.liang@intel.com> (raw)
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
Changes since V6:
- Add error infor for per-event time
- rename the option to call-graph and stacl-size
- refine parse/config callchain functions,
and reuse them for per-event callgraph setting
- Modify perf test
Changes since V7:
- Rebase on 6ea3269c58
- Enclose callgraph reset codes.
Kan Liang (4):
perf,tools: per-event time support
perf,tools: refine parse/config callchain functions
perf,tools: per-event callgraph support
perf,tests: Add tests to callgraph and time parse
tools/perf/Documentation/perf-record.txt | 8 ++-
tools/perf/builtin-record.c | 2 +-
tools/perf/tests/parse-events.c | 38 ++++++++++++++
tools/perf/util/callchain.c | 14 +++---
tools/perf/util/callchain.h | 2 +-
tools/perf/util/evsel.c | 86 +++++++++++++++++++++++++++++---
tools/perf/util/evsel.h | 6 +++
tools/perf/util/parse-events.c | 24 +++++++++
tools/perf/util/parse-events.h | 3 ++
tools/perf/util/parse-events.l | 3 ++
tools/perf/util/pmu.c | 3 +-
11 files changed, 170 insertions(+), 19 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-08-04 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 8:30 Kan Liang [this message]
2015-08-04 8:30 ` [PATCH RFC V8 1/4] perf,tools: per-event " Kan Liang
2015-08-05 7:18 ` Jiri Olsa
2015-08-06 7:02 ` [tip:perf/core] perf tools: Per-event " tip-bot for Kan Liang
2015-08-04 8:30 ` [PATCH RFC V8 2/4] perf,tools: refine parse/config callchain functions Kan Liang
2015-08-05 7:18 ` Jiri Olsa
2015-08-06 7:03 ` [tip:perf/core] perf tools: Refine parse/ config " tip-bot for Kan Liang
2015-08-04 8:30 ` [PATCH RFC V8 3/4] perf,tools: per-event callgraph support Kan Liang
2015-08-05 7:21 ` Jiri Olsa
2015-08-05 7:28 ` Jiri Olsa
2015-08-05 15:45 ` Liang, Kan
2015-08-06 18:55 ` Arnaldo Carvalho de Melo
2015-08-04 8:30 ` [PATCH RFC V8 4/4] perf,tests: Add tests to callgraph and time parse Kan Liang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1438677022-34296-1-git-send-email-kan.liang@intel.com \
--to=kan.liang@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®