LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] perf: Document default event for perf record
Date: Mon, 24 Jan 2011 14:16:14 +0100	[thread overview]
Message-ID: <87aaiqjvc1.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <20110124131050.GA6367@ghostprotocols.net>

The description of -e option was reformatted (unindented and enclosed
in an OpenBlock) in order to render the added line correctly.

Signed-off-by: Michal Sojka <sojkam1@fel.cvut.cz>
---
 tools/perf/Documentation/perf-record.txt |   28 ++++++++++++++++------------
 1 files changed, 16 insertions(+), 12 deletions(-)

diff --git a/tools/perf/Documentation/perf-record.txt b/tools/perf/Documentation/perf-record.txt
index e032716..bfcf3f2 100644
--- a/tools/perf/Documentation/perf-record.txt
+++ b/tools/perf/Documentation/perf-record.txt
@@ -27,18 +27,22 @@ OPTIONS
 -e::
 --event=::
 	Select the PMU event. Selection can be:
-
-        - a symbolic event name	(use 'perf list' to list all events)
-
-        - a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
-	  hexadecimal event descriptor.
-
-        - a hardware breakpoint event in the form of '\mem:addr[:access]'
-          where addr is the address in memory you want to break in.
-          Access is the memory access type (read, write, execute) it can
-          be passed as follows: '\mem:addr[:[r][w][x]]'.
-          If you want to profile read-write accesses in 0x1000, just set
-          'mem:0x1000:rw'.
++
+--
+- a symbolic event name	(use 'perf list' to list all events)
+
+- a raw PMU event (eventsel+umask) in the form of rNNN where NNN is a
+  hexadecimal event descriptor.
+
+- a hardware breakpoint event in the form of '\mem:addr[:access]'
+  where addr is the address in memory you want to break in.
+  Access is the memory access type (read, write, execute) it can
+  be passed as follows: '\mem:addr[:[r][w][x]]'.
+  If you want to profile read-write accesses in 0x1000, just set
+  'mem:0x1000:rw'.
+
+By default, 'cpu-cycles' event is selected.
+--
 
 --filter=<filter>::
         Event filter.
-- 
1.7.2.3


      reply	other threads:[~2011-01-24 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22 11:18 Michal Sojka
2011-01-24 13:05 ` Arnaldo Carvalho de Melo
2011-01-24 13:10   ` Arnaldo Carvalho de Melo
2011-01-24 13:16     ` Michal Sojka [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=87aaiqjvc1.fsf@steelpick.2x.cz \
    --to=sojkam1@fel.cvut.cz \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --subject='Re: [PATCH] perf: Document default event for perf record' \
    /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

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).