Re: [PATCH] perf: Document default event for perf record

[Michal Sojka]

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@xxxxxxxxxxx>
---
 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/