From: Jiri Olsa <jolsa@redhat.com>
To: kan.liang@intel.com
Cc: acme@kernel.org, namhyung@kernel.org, jolsa@kernel.org,
ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/1] perf,tool: partial callgrap and time support
Date: Tue, 30 Jun 2015 14:31:17 +0200 [thread overview]
Message-ID: <20150630123117.GG25631@krava.brq.redhat.com> (raw)
In-Reply-To: <1435513641-9139-1-git-send-email-kan.liang@intel.com>
On Sun, Jun 28, 2015 at 01:47:21PM -0400, kan.liang@intel.com wrote:
SNIP
> Signed-off-by: Kan Liang <kan.liang@intel.com>
> ---
> tools/perf/Documentation/perf-record.txt | 13 ++++++++
> tools/perf/builtin-record.c | 7 ++--
> tools/perf/perf.h | 2 ++
> tools/perf/util/evsel.c | 55 ++++++++++++++++++++++++++++++--
> tools/perf/util/parse-events.c | 33 +++++++++++++++++++
> tools/perf/util/parse-events.h | 3 ++
> tools/perf/util/parse-events.l | 3 ++
> tools/perf/util/parse-options.c | 2 ++
> tools/perf/util/parse-options.h | 4 +++
> 9 files changed, 116 insertions(+), 6 deletions(-)
>
> diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
> index 9b9d9d0..f945b01 100644
> --- a/tools/perf/Documentation/perf-record.txt
> +++ b/tools/perf/Documentation/perf-record.txt
> @@ -45,6 +45,19 @@ OPTIONS
> param1 and param2 are defined as formats for the PMU in:
> /sys/bus/event_sources/devices/<pmu>/format/*
>
> + There are also some params which are not defined in .../<pmu>/format/*.
> + These params can be used to set event defaults.
> + Here is a list of the params.
> + - 'period': Set event sampling period
> + - 'callgraph': Disable/enable callgraph. Acceptable values are
> + 1 for FP mode, 2 for dwarf mode, 3 for LBR mode,
> + 0 for disabling callgraph.
why dont use strings like 'fp,dwarf,lbr' to identify callchains?
you'd have:
'{cpu/cpu-cycles,callgraph=fp,time=1,period=100000/,
also you dont need to assign 1 to time, it's the default, so this is equal:
'{cpu/cpu-cycles,callgraph=fp,time,period=100000/,
come to that, 'fp' could be default for callgraph, like:
'{cpu/cpu-cycles,callgraph,time,period=100000/,
we already have string terms translation support
in pmu_config_term.. but I guess this is not pmu specific
and can stay in config_term
also please add appropriate tests to tests/parse-events.c
thanks,
jirka
next prev parent reply other threads:[~2015-06-30 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 17:47 kan.liang
2015-06-30 12:31 ` Jiri Olsa [this message]
2015-06-30 12:34 ` 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=20150630123117.GG25631@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=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
all inboxes | Powered by JetHome®