From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Kan Liang <kan.liang@intel.com>
Cc: jolsa@kernel.org, namhyung@kernel.org, ak@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC V7 0/7] per event callgraph and time support
Date: Wed, 29 Jul 2015 16:20:38 -0300 [thread overview]
Message-ID: <20150729192038.GK575@kernel.org> (raw)
In-Reply-To: <1438162936-59698-1-git-send-email-kan.liang@intel.com>
Em Wed, Jul 29, 2015 at 05:42:09AM -0400, Kan Liang escreveu:
> 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.
Applied the first three patches, will wait for Jiri comments on the
remaining.
- Arnaldo
> 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
>
> Jiri Olsa (2):
> perf tools: Add support for event post configuration
> perf tools: Force period term to overload global settings
>
> Kan Liang (5):
> perf,tools: introduce callgraph_set for callgraph option
> 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 | 10 ++-
> tools/perf/builtin-record.c | 11 +++-
> tools/perf/perf.h | 1 +
> tools/perf/tests/parse-events.c | 50 ++++++++++++++-
> tools/perf/util/callchain.c | 14 ++---
> tools/perf/util/callchain.h | 2 +-
> tools/perf/util/evsel.c | 105 +++++++++++++++++++++++++++++--
> tools/perf/util/evsel.h | 26 ++++++++
> tools/perf/util/parse-events.c | 94 +++++++++++++++++++++++----
> tools/perf/util/parse-events.h | 3 +
> tools/perf/util/parse-events.l | 3 +
> tools/perf/util/pmu.c | 3 +-
> 12 files changed, 289 insertions(+), 33 deletions(-)
>
> --
> 1.8.3.1
prev parent reply other threads:[~2015-07-29 19:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 9:42 [PATCH RFC V7 0/7] per event callgraph and time support Kan Liang
2015-07-29 9:42 ` [PATCH RFC V7 1/7] perf tools: Add support for event post configuration Kan Liang
2015-07-31 13:54 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-07-29 9:42 ` [PATCH RFC V7 2/7] perf tools: Force period term to overload global settings Kan Liang
2015-07-31 13:54 ` [tip:perf/core] " tip-bot for Jiri Olsa
2015-07-29 9:42 ` [PATCH RFC V7 3/7] perf,tools: introduce callgraph_set for callgraph option Kan Liang
2015-07-31 13:54 ` [tip:perf/core] perf tools: Introduce " tip-bot for Kan Liang
2015-07-29 9:42 ` [PATCH RFC V7 4/7] perf,tools: per-event time support Kan Liang
2015-07-29 9:42 ` [PATCH RFC V7 5/7] perf,tools: refine parse/config callchain functions Kan Liang
2015-07-29 9:42 ` [PATCH RFC V7 6/7] perf,tools: per-event callgraph support Kan Liang
2015-07-30 12:15 ` Jiri Olsa
2015-07-29 9:42 ` [PATCH RFC V7 7/7] perf,tests: Add tests to callgraph and time parse Kan Liang
2015-07-29 19:20 ` Arnaldo Carvalho de Melo [this message]
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=20150729192038.GK575@kernel.org \
--to=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).