From: tip-bot for Kan Liang <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: kan.liang@intel.com, acme@redhat.com,
linux-kernel@vger.kernel.org, namhyung@kernel.org, hpa@zytor.com,
tglx@linutronix.de, mingo@kernel.org, ak@linux.intel.com,
jolsa@kernel.org
Subject: [tip:perf/core] perf record: Document setting '-e pmu/period=N/' in man page
Date: Tue, 21 Jul 2015 02:31:39 -0700 [thread overview]
Message-ID: <tip-3d5d68aabf4ff47cfb447ad90448ce50531be7f5@git.kernel.org> (raw)
In-Reply-To: <1436345097-11113-3-git-send-email-kan.liang@intel.com>
Commit-ID: 3d5d68aabf4ff47cfb447ad90448ce50531be7f5
Gitweb: http://git.kernel.org/tip/3d5d68aabf4ff47cfb447ad90448ce50531be7f5
Author: Kan Liang <kan.liang@intel.com>
AuthorDate: Wed, 8 Jul 2015 04:44:54 -0400
Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
CommitDate: Tue, 14 Jul 2015 07:52:00 -0300
perf record: Document setting '-e pmu/period=N/' in man page
The 'period' param is not defined in
/sys/bus/event_sources/devices/<pmu>/format/*, but can be used, document
it.
Signed-off-by: Kan Liang <kan.liang@intel.com>
Acked-by: Jiri Olsa <jolsa@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>
Link: http://lkml.kernel.org/r/1436345097-11113-3-git-send-email-kan.liang@intel.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/Documentation/perf-record.txt | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
index 9b9d9d0..5b47b2c 100644
--- a/tools/perf/Documentation/perf-record.txt
+++ b/tools/perf/Documentation/perf-record.txt
@@ -45,6 +45,14 @@ 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
+
+ Note: If user explicitly sets options which conflict with the params,
+ the value set by the params will be overridden.
+
- a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
where addr is the address in memory you want to break in.
Access is the memory access type (read, write, execute) it can
next prev parent reply other threads:[~2015-07-21 9:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 8:44 [PATCH RFC V3 0/5] partial callgrap and time support kan.liang
2015-07-08 8:44 ` [PATCH RFC V3 1/5] perf,tools: introduce OPT_CALLBACK_SET/OPT_CALLBACK_NOOPT_SET kan.liang
2015-07-14 6:54 ` Jiri Olsa
2015-07-08 8:44 ` [PATCH RFC V3 2/5] perf/documentation: Add description for period kan.liang
2015-07-14 6:55 ` Jiri Olsa
2015-07-14 14:05 ` Arnaldo Carvalho de Melo
2015-07-21 9:31 ` tip-bot for Kan Liang [this message]
2015-07-08 8:44 ` [PATCH RFC V3 3/5] perf,tool: partial time support kan.liang
2015-07-13 13:27 ` Namhyung Kim
2015-07-13 19:01 ` Liang, Kan
2015-07-14 1:04 ` Namhyung Kim
2015-07-15 19:03 ` Liang, Kan
2015-07-17 7:12 ` Namhyung Kim
2015-07-14 6:54 ` Jiri Olsa
2015-07-14 6:54 ` Jiri Olsa
2015-07-08 8:44 ` [PATCH RFC V3 4/5] perf,tool: partial callgrap support kan.liang
2015-07-08 8:44 ` [PATCH RFC V3 5/5] 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=tip-3d5d68aabf4ff47cfb447ad90448ce50531be7f5@git.kernel.org \
--to=tipbot@zytor.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
/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).