perf/documentation: Fix typo in perf/Documentation
PATCH 1/1 perf/documentation: Fix typo in perf/Documentation
This patch fix spelling typo found in tool/perf/Documentation.
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)
tools/perf/Documentation/perf-diff.txt +3 -3
@@ -196,10 +196,10 @@ If specified the 'Weighted diff' column is displayed with value 'd' computed as: - period being the hist entry period value - - WEIGHT-A/WEIGHT-B being user suplied weights in the the '-c' option + - WEIGHT-A/WEIGHT-B being user supplied weights in the the '-c' option behind ':' separator like '-c wdiff:1,2'. - - WIEGHT-A being the weight of the data file - - WIEGHT-B being the weight of the baseline data file + - WEIGHT-A being the weight of the data file + - WEIGHT-B being the weight of the baseline data file SEE ALSO --------
tools/perf/Documentation/perf-kvm.txt +2 -2
@@ -100,7 +100,7 @@ OPTIONS STAT REPORT OPTIONS ------------------- --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurres on this vcpu. (default: all vcpus) --event=<value>:: event to be analyzed. Possible values: vmexit, mmio (x86 only),
@@ -134,7 +134,7 @@ STAT LIVE OPTIONS Analyze events only for given process ID(s) (comma separated list). --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurres on this vcpu. (default: all vcpus) --event=<value>::
tools/perf/Documentation/perf-list.txt +1 -1
@@ -19,7 +19,7 @@ various perf commands with the -e option. EVENT MODIFIERS --------------- -Events can optionally have a modifer by appending a colon and one or +Events can optionally have a modifier by appending a colon and one or more modifiers. Modifiers allow the user to restrict the events to be counted. The following modifiers exist:
tools/perf/Documentation/perf-record.txt +1 -1
@@ -146,7 +146,7 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs. -N:: --no-buildid-cache:: -Do not update the builid cache. This saves some overhead in situations +Do not update the buildid cache. This saves some overhead in situations where the information in the perf.data file (which includes buildids) is sufficient.
tools/perf/Documentation/perf-script-perl.txt +2 -2
@@ -181,8 +181,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the flag field $field_name of event $event_name - symbol_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the symbolic field $field_name of event $event_name + flag_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the flag field $field_name of event $event_name + symbol_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the symbolic field $field_name of event $event_name Perf::Trace::Context Module ~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/perf/Documentation/perf-script-python.txt +3 -3
@@ -263,7 +263,7 @@ and having the counts we've tallied as values. The print_syscall_totals() function iterates over the entries in the dictionary and displays a line for each entry containing the syscall -name (the dictonary keys contain the syscall ids, which are passed to +name (the dictionary keys contain the syscall ids, which are passed to the Util function syscall_name(), which translates the raw syscall numbers to the corresponding syscall name strings). The output is displayed after all the events in the trace have been processed, by
@@ -576,8 +576,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the flag field field_name of event event_name - symbol_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the symbolic field field_name of event event_name + flag_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the flag field field_name of event event_name + symbol_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the symbolic field field_name of event event_name The *autodict* function returns a special kind of Python dictionary that implements Perl's 'autovivifying' hashes in Python
tools/perf/Documentation/perf-script.txt +1 -1
@@ -140,7 +140,7 @@ OPTIONS "Overriding previous field request for all events." - Alternativey, consider the order: + Alternatively, consider the order: -f comm,tid,time,ip,sym -f trace:
tools/perf/Documentation/perf-test.txt +1 -1
@@ -25,7 +25,7 @@ OPTIONS ------- -s:: --skip:: - Tests to skip (comma separater numeric list). + Tests to skip (comma separator numeric list). -v:: --verbose::
tools/perf/Documentation/perf-trace.txt +1 -1
@@ -20,7 +20,7 @@ scheduling events, etc. This is a live mode tool in addition to working with perf.data files like the other perf tools. Files can be generated using the 'perf record' command but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*'). -Alernatively, the 'perf trace record' can be used as a shortcut to +Alternatively, the 'perf trace record' can be used as a shortcut to automatically include the raw_syscalls events when writing events to a file. The following options apply to perf trace; options to perf trace record are
Signature · 1 line
2.1.0.24.g4109c28
Quoted 20 lines · Masanari Iida
This patch fix spelling typo found in tool/perf/Documentation.
Signed-off-by Masanari Iida <[email protected]>--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)tools/perf/Documentation/perf-kvm.txt +0
-0
tools/perf/Documentation/perf-kvm.txt OPTIONS · line 103
Quoted 5 lines
tools/perf/Documentation/perf-kvm.txt +1
-1@@ -100,7 +100,7 @@ OPTIONS STAT REPORT OPTIONS ------------------- --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurres on this vcpu. (default: all vcpus)
occurs
tools/perf/Documentation/perf-kvm.txt STAT LIVE OPTIONS · line 137
Quoted 9 lines
tools/perf/Documentation/perf-kvm.txt +1
-1--event=<value>:: event to be analyzed. Possible values: vmexit, mmio (x86 only),@@ -134,7 +134,7 @@ STAT LIVE OPTIONS Analyze events only for given process ID(s) (comma separated list). --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurres on this vcpu. (default: all vcpus)
occurs
Quoted 3 lines
tools/perf/Documentation/perf-kvm.txt +0
-0--event=<value>::
Signature · 1 line
~Randy
This patch fix spelling typo found in tool/perf/Documentation.
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)
tools/perf/Documentation/perf-diff.txt +3 -3
@@ -196,10 +196,10 @@ If specified the 'Weighted diff' column is displayed with value 'd' computed as: - period being the hist entry period value - - WEIGHT-A/WEIGHT-B being user suplied weights in the the '-c' option + - WEIGHT-A/WEIGHT-B being user supplied weights in the the '-c' option behind ':' separator like '-c wdiff:1,2'. - - WIEGHT-A being the weight of the data file - - WIEGHT-B being the weight of the baseline data file + - WEIGHT-A being the weight of the data file + - WEIGHT-B being the weight of the baseline data file SEE ALSO --------
tools/perf/Documentation/perf-kvm.txt +2 -2
@@ -100,7 +100,7 @@ OPTIONS STAT REPORT OPTIONS ------------------- --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurs on this vcpu. (default: all vcpus) --event=<value>:: event to be analyzed. Possible values: vmexit, mmio (x86 only),
@@ -134,7 +134,7 @@ STAT LIVE OPTIONS Analyze events only for given process ID(s) (comma separated list). --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurs on this vcpu. (default: all vcpus) --event=<value>::
tools/perf/Documentation/perf-list.txt +1 -1
@@ -19,7 +19,7 @@ various perf commands with the -e option. EVENT MODIFIERS --------------- -Events can optionally have a modifer by appending a colon and one or +Events can optionally have a modifier by appending a colon and one or more modifiers. Modifiers allow the user to restrict the events to be counted. The following modifiers exist:
tools/perf/Documentation/perf-record.txt +1 -1
@@ -146,7 +146,7 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs. -N:: --no-buildid-cache:: -Do not update the builid cache. This saves some overhead in situations +Do not update the buildid cache. This saves some overhead in situations where the information in the perf.data file (which includes buildids) is sufficient.
tools/perf/Documentation/perf-script-perl.txt +2 -2
@@ -181,8 +181,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the flag field $field_name of event $event_name - symbol_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the symbolic field $field_name of event $event_name + flag_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the flag field $field_name of event $event_name + symbol_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the symbolic field $field_name of event $event_name Perf::Trace::Context Module ~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/perf/Documentation/perf-script-python.txt +3 -3
@@ -263,7 +263,7 @@ and having the counts we've tallied as values. The print_syscall_totals() function iterates over the entries in the dictionary and displays a line for each entry containing the syscall -name (the dictonary keys contain the syscall ids, which are passed to +name (the dictionary keys contain the syscall ids, which are passed to the Util function syscall_name(), which translates the raw syscall numbers to the corresponding syscall name strings). The output is displayed after all the events in the trace have been processed, by
@@ -576,8 +576,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the flag field field_name of event event_name - symbol_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the symbolic field field_name of event event_name + flag_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the flag field field_name of event event_name + symbol_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the symbolic field field_name of event event_name The *autodict* function returns a special kind of Python dictionary that implements Perl's 'autovivifying' hashes in Python
tools/perf/Documentation/perf-script.txt +1 -1
@@ -140,7 +140,7 @@ OPTIONS "Overriding previous field request for all events." - Alternativey, consider the order: + Alternatively, consider the order: -f comm,tid,time,ip,sym -f trace:
tools/perf/Documentation/perf-test.txt +1 -1
@@ -25,7 +25,7 @@ OPTIONS ------- -s:: --skip:: - Tests to skip (comma separater numeric list). + Tests to skip (comma separator numeric list). -v:: --verbose::
tools/perf/Documentation/perf-trace.txt +1 -1
@@ -20,7 +20,7 @@ scheduling events, etc. This is a live mode tool in addition to working with perf.data files like the other perf tools. Files can be generated using the 'perf record' command but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*'). -Alernatively, the 'perf trace record' can be used as a shortcut to +Alternatively, the 'perf trace record' can be used as a shortcut to automatically include the raw_syscalls events when writing events to a file. The following options apply to perf trace; options to perf trace record are
Signature · 1 line
2.1.0.24.g4109c28
Quoted 3 lines · Masanari Iida
This patch fix spelling typo found in tool/perf/Documentation.
Signed-off-by Masanari Iida <[email protected]>
Sorry, I found a few more items that could be fixed... and I seem to have mucked up yesterday's comments. :(
Quoted 17 lines
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)tools/perf/Documentation/perf-kvm.txt +0
-0
tools/perf/Documentation/perf-kvm.txt OPTIONS · line 103
Quoted 5 lines
tools/perf/Documentation/perf-kvm.txt +1
-1@@ -100,7 +100,7 @@ OPTIONS STAT REPORT OPTIONS ------------------- --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurs on this vcpu. (default: all vcpus)
occur
tools/perf/Documentation/perf-kvm.txt STAT LIVE OPTIONS · line 137
Quoted 9 lines
tools/perf/Documentation/perf-kvm.txt +1
-1--event=<value>:: event to be analyzed. Possible values: vmexit, mmio (x86 only),@@ -134,7 +134,7 @@ STAT LIVE OPTIONS Analyze events only for given process ID(s) (comma separated list). --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occurs on this vcpu. (default: all vcpus)
occur
tools/perf/Documentation/perf-test.txt OPTIONS · line 28
Quoted 13 lines
tools/perf/Documentation/perf-kvm.txt +0
-0--event=<value>::tools/perf/Documentation/perf-test.txt +1
-1@@ -25,7 +25,7 @@ OPTIONS ------- -s:: --skip:: - Tests to skip (comma separater numeric list). + Tests to skip (comma separator numeric list).
separated
tools/perf/Documentation/perf-trace.txt scheduling events, etc. · line 23
Quoted 13 lines
tools/perf/Documentation/perf-test.txt +0
-0-v:: --verbose::tools/perf/Documentation/perf-trace.txt +1
-1@@ -20,7 +20,7 @@ scheduling events, etc. This is a live mode tool in addition to working with perf.data files like the other perf tools. Files can be generated using the 'perf record' command but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*'). -Alernatively, the 'perf trace record' can be used as a shortcut to +Alternatively, the 'perf trace record' can be used as a shortcut to
either:
the 'perf trace record' command can be used ...
or
'perf trace record' can be used ...
tools/perf/Documentation/perf-trace.txt scheduling events, etc. · line 26
Quoted 4 lines
tools/perf/Documentation/perf-trace.txt +0
-0automatically include the raw_syscalls events when writing events to a file. The following options apply to perf trace; options to perf trace record are
Thanks.
Signature · 1 line
~Randy
This patch fix spelling typo found in tool/perf/Documentation.
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)
tools/perf/Documentation/perf-diff.txt +3 -3
@@ -196,10 +196,10 @@ If specified the 'Weighted diff' column is displayed with value 'd' computed as: - period being the hist entry period value - - WEIGHT-A/WEIGHT-B being user suplied weights in the the '-c' option + - WEIGHT-A/WEIGHT-B being user supplied weights in the the '-c' option behind ':' separator like '-c wdiff:1,2'. - - WIEGHT-A being the weight of the data file - - WIEGHT-B being the weight of the baseline data file + - WEIGHT-A being the weight of the data file + - WEIGHT-B being the weight of the baseline data file SEE ALSO --------
tools/perf/Documentation/perf-kvm.txt +2 -2
@@ -100,7 +100,7 @@ OPTIONS STAT REPORT OPTIONS ------------------- --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occur on this vcpu. (default: all vcpus) --event=<value>:: event to be analyzed. Possible values: vmexit, mmio (x86 only),
@@ -134,7 +134,7 @@ STAT LIVE OPTIONS Analyze events only for given process ID(s) (comma separated list). --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occur on this vcpu. (default: all vcpus) --event=<value>::
tools/perf/Documentation/perf-list.txt +1 -1
@@ -19,7 +19,7 @@ various perf commands with the -e option. EVENT MODIFIERS --------------- -Events can optionally have a modifer by appending a colon and one or +Events can optionally have a modifier by appending a colon and one or more modifiers. Modifiers allow the user to restrict the events to be counted. The following modifiers exist:
tools/perf/Documentation/perf-record.txt +1 -1
@@ -146,7 +146,7 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs. -N:: --no-buildid-cache:: -Do not update the builid cache. This saves some overhead in situations +Do not update the buildid cache. This saves some overhead in situations where the information in the perf.data file (which includes buildids) is sufficient.
tools/perf/Documentation/perf-script-perl.txt +2 -2
@@ -181,8 +181,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the flag field $field_name of event $event_name - symbol_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the symbolic field $field_name of event $event_name + flag_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the flag field $field_name of event $event_name + symbol_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the symbolic field $field_name of event $event_name Perf::Trace::Context Module ~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/perf/Documentation/perf-script-python.txt +3 -3
@@ -263,7 +263,7 @@ and having the counts we've tallied as values. The print_syscall_totals() function iterates over the entries in the dictionary and displays a line for each entry containing the syscall -name (the dictonary keys contain the syscall ids, which are passed to +name (the dictionary keys contain the syscall ids, which are passed to the Util function syscall_name(), which translates the raw syscall numbers to the corresponding syscall name strings). The output is displayed after all the events in the trace have been processed, by
@@ -576,8 +576,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the flag field field_name of event event_name - symbol_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the symbolic field field_name of event event_name + flag_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the flag field field_name of event event_name + symbol_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the symbolic field field_name of event event_name The *autodict* function returns a special kind of Python dictionary that implements Perl's 'autovivifying' hashes in Python
tools/perf/Documentation/perf-script.txt +1 -1
@@ -140,7 +140,7 @@ OPTIONS "Overriding previous field request for all events." - Alternativey, consider the order: + Alternatively, consider the order: -f comm,tid,time,ip,sym -f trace:
tools/perf/Documentation/perf-test.txt +1 -1
@@ -25,7 +25,7 @@ OPTIONS ------- -s:: --skip:: - Tests to skip (comma separater numeric list). + Tests to skip (comma separated numeric list). -v:: --verbose::
tools/perf/Documentation/perf-trace.txt +1 -1
@@ -20,7 +20,7 @@ scheduling events, etc. This is a live mode tool in addition to working with perf.data files like the other perf tools. Files can be generated using the 'perf record' command but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*'). -Alernatively, the 'perf trace record' can be used as a shortcut to +Alternatively, 'perf trace record' can be used as a shortcut to automatically include the raw_syscalls events when writing events to a file. The following options apply to perf trace; options to perf trace record are
Signature · 1 line
2.1.0.60.g85f0837
Randy Dunlap
Acked-byQuoted 3 lines · Masanari Iida
This patch fix spelling typo found in tool/perf/Documentation.
Signed-off-by Masanari Iida <[email protected]>
Thanks.
Quoted 11 lines
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)
Signature · 1 line
~Randy
Em Tue, Sep 09, 2014 at 01:46:11PM -0700, Randy Dunlap escreveu:
Quoted 6 lines · Masanari Iida
Quoted 3 lines
This patch fix spelling typo found in tool/perf/Documentation.
Signed-off-by Masanari Iida <[email protected]>Acked-by Randy Dunlap <[email protected]>
Thanks, applied.
Quoted 17 lines
Thanks.
Quoted 11 lines
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)Signature · 1 line
~Randy
tip-bot for Masanari Iida
merge bot[tip:perf/urgent] perf Documentation: Fix typos in perf/ Documentation
In reply to Masanari Iidaperf Documentation: Fix typos in perf/Documentation
Commit-ID: 96355f2cfb61bb057df9bc0712cd7323dba28080 Gitweb: http://git.kernel.org/tip/96355f2cfb61bb057df9bc0712cd7323dba28080 Author: Masanari Iida <[email protected]> AuthorDate: Wed, 10 Sep 2014 00:18:50 +0900 Committer: Arnaldo Carvalho de Melo <[email protected]> CommitDate: Wed, 15 Oct 2014 17:39:02 -0300
perf Documentation: Fix typos in perf/Documentation
This patch fix spelling typos found in tool/perf/Documentation.
--- tools/perf/Documentation/perf-diff.txt | 6 +++--- tools/perf/Documentation/perf-kvm.txt | 4 ++-- tools/perf/Documentation/perf-list.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- tools/perf/Documentation/perf-script-perl.txt | 4 ++-- tools/perf/Documentation/perf-script-python.txt | 6 +++--- tools/perf/Documentation/perf-script.txt | 2 +- tools/perf/Documentation/perf-test.txt | 2 +- tools/perf/Documentation/perf-trace.txt | 2 +- 9 files changed, 15 insertions(+), 15 deletions(-)
tools/perf/Documentation/perf-diff.txt +3 -3
@@ -196,10 +196,10 @@ If specified the 'Weighted diff' column is displayed with value 'd' computed as: - period being the hist entry period value - - WEIGHT-A/WEIGHT-B being user suplied weights in the the '-c' option + - WEIGHT-A/WEIGHT-B being user supplied weights in the the '-c' option behind ':' separator like '-c wdiff:1,2'. - - WIEGHT-A being the weight of the data file - - WIEGHT-B being the weight of the baseline data file + - WEIGHT-A being the weight of the data file + - WEIGHT-B being the weight of the baseline data file SEE ALSO --------
tools/perf/Documentation/perf-kvm.txt +2 -2
@@ -100,7 +100,7 @@ OPTIONS STAT REPORT OPTIONS ------------------- --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occur on this vcpu. (default: all vcpus) --event=<value>:: event to be analyzed. Possible values: vmexit, mmio (x86 only),
@@ -134,7 +134,7 @@ STAT LIVE OPTIONS Analyze events only for given process ID(s) (comma separated list). --vcpu=<value>:: - analyze events which occures on this vcpu. (default: all vcpus) + analyze events which occur on this vcpu. (default: all vcpus) --event=<value>::
tools/perf/Documentation/perf-list.txt +1 -1
@@ -19,7 +19,7 @@ various perf commands with the -e option. EVENT MODIFIERS --------------- -Events can optionally have a modifer by appending a colon and one or +Events can optionally have a modifier by appending a colon and one or more modifiers. Modifiers allow the user to restrict the events to be counted. The following modifiers exist:
tools/perf/Documentation/perf-record.txt +1 -1
@@ -146,7 +146,7 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs. -N:: --no-buildid-cache:: -Do not update the builid cache. This saves some overhead in situations +Do not update the buildid cache. This saves some overhead in situations where the information in the perf.data file (which includes buildids) is sufficient.
tools/perf/Documentation/perf-script-perl.txt +2 -2
@@ -181,8 +181,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the flag field $field_name of event $event_name - symbol_str($event_name, $field_name, $field_value) - returns the string represention corresponding to $field_value for the symbolic field $field_name of event $event_name + flag_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the flag field $field_name of event $event_name + symbol_str($event_name, $field_name, $field_value) - returns the string representation corresponding to $field_value for the symbolic field $field_name of event $event_name Perf::Trace::Context Module ~~~~~~~~~~~~~~~~~~~~~~~~~~~
tools/perf/Documentation/perf-script-python.txt +3 -3
@@ -263,7 +263,7 @@ and having the counts we've tallied as values. The print_syscall_totals() function iterates over the entries in the dictionary and displays a line for each entry containing the syscall -name (the dictonary keys contain the syscall ids, which are passed to +name (the dictionary keys contain the syscall ids, which are passed to the Util function syscall_name(), which translates the raw syscall numbers to the corresponding syscall name strings). The output is displayed after all the events in the trace have been processed, by
@@ -576,8 +576,8 @@ strings for flag and symbolic fields. These correspond to the strings and values parsed from the 'print fmt' fields of the event format files: - flag_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the flag field field_name of event event_name - symbol_str(event_name, field_name, field_value) - returns the string represention corresponding to field_value for the symbolic field field_name of event event_name + flag_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the flag field field_name of event event_name + symbol_str(event_name, field_name, field_value) - returns the string representation corresponding to field_value for the symbolic field field_name of event event_name The *autodict* function returns a special kind of Python dictionary that implements Perl's 'autovivifying' hashes in Python
tools/perf/Documentation/perf-script.txt +1 -1
@@ -140,7 +140,7 @@ OPTIONS "Overriding previous field request for all events." - Alternativey, consider the order: + Alternatively, consider the order: -f comm,tid,time,ip,sym -f trace:
tools/perf/Documentation/perf-test.txt +1 -1
@@ -25,7 +25,7 @@ OPTIONS ------- -s:: --skip:: - Tests to skip (comma separater numeric list). + Tests to skip (comma separated numeric list). -v:: --verbose::
tools/perf/Documentation/perf-trace.txt +1 -1
@@ -20,7 +20,7 @@ scheduling events, etc. This is a live mode tool in addition to working with perf.data files like the other perf tools. Files can be generated using the 'perf record' command but the session needs to include the raw_syscalls events (-e 'raw_syscalls:*'). -Alernatively, the 'perf trace record' can be used as a shortcut to +Alternatively, 'perf trace record' can be used as a shortcut to automatically include the raw_syscalls events when writing events to a file. The following options apply to perf trace; options to perf trace record are