mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 V6 0/6] per event callgraph and time support
Date: Mon, 27 Jul 2015 08:21:33 -0400	[thread overview]
Message-ID: <1437999699-19632-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

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


             reply	other threads:[~2015-07-27 19:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-27 12:21 Kan Liang [this message]
2015-07-27 12:21 ` [PATCH RFC V6 1/6] perf tools: Add support for event post configuration Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 2/6] perf tools: Force period term to overload global settings Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 3/6] perf,tools: introduce callgraph_set for callgraph option Kan Liang
2015-07-27 12:21 ` [PATCH RFC V6 4/6] perf,tool: per-event time support Kan Liang
2015-07-29 11:02   ` Jiri Olsa
2015-07-27 12:21 ` [PATCH RFC V6 5/6] perf,tool: per-event callgraph support Kan Liang
2015-07-29 11:20   ` Jiri Olsa
2015-07-29 11:48   ` Jiri Olsa
2015-07-29 11:50   ` Jiri Olsa
2015-07-27 12:21 ` [PATCH RFC V6 6/6] perf,tests: Add tests to callgraph and time parse Kan Liang
2015-07-29 11:53   ` Jiri Olsa

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=1437999699-19632-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®