public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: 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 V4 0/4] per event callgrap and time support
Date: Thu, 16 Jul 2015 04:26:06 -0400	[thread overview]
Message-ID: <1437035170-12911-1-git-send-email-kan.liang@intel.com> (raw)

From: Kan Liang <kan.liang@intel.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


             reply	other threads:[~2015-07-16 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16  8:26 kan.liang [this message]
2015-07-16  8:26 ` [PATCH RFC V4 1/4] perf,tools: introduce callgraph_set for callgraph option kan.liang
2015-07-17  9:23   ` Jiri Olsa
2015-07-17 14:24     ` Liang, Kan
2015-07-16  8:26 ` [PATCH RFC V4 2/4] perf,tool: per-event time support kan.liang
2015-07-16  8:26 ` [PATCH RFC V4 3/4] perf,tool: per-event callgrap support kan.liang
2015-07-16  8:26 ` [PATCH RFC V4 4/4] perf,tests: Add tests to callgrap 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=1437035170-12911-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