diff options
Diffstat (limited to 'tools/perf/Documentation/perf-trace-python.txt')
-rw-r--r-- | tools/perf/Documentation/perf-trace-python.txt | 16 |
1 files changed, 7 insertions, 9 deletions
diff --git a/tools/perf/Documentation/perf-trace-python.txt b/tools/perf/Documentation/perf-trace-python.txt index a241aca77184..693be804dd3d 100644 --- a/tools/perf/Documentation/perf-trace-python.txt +++ b/tools/perf/Documentation/perf-trace-python.txt | |||
@@ -1,5 +1,5 @@ | |||
1 | perf-trace-python(1) | 1 | perf-trace-python(1) |
2 | ================== | 2 | ==================== |
3 | 3 | ||
4 | NAME | 4 | NAME |
5 | ---- | 5 | ---- |
@@ -93,7 +93,7 @@ don't care how it exited, so we'll use 'perf record' to record only | |||
93 | the sys_enter events: | 93 | the sys_enter events: |
94 | 94 | ||
95 | ---- | 95 | ---- |
96 | # perf record -c 1 -f -a -M -R -e raw_syscalls:sys_enter | 96 | # perf record -a -e raw_syscalls:sys_enter |
97 | 97 | ||
98 | ^C[ perf record: Woken up 1 times to write data ] | 98 | ^C[ perf record: Woken up 1 times to write data ] |
99 | [ perf record: Captured and wrote 56.545 MB perf.data (~2470503 samples) ] | 99 | [ perf record: Captured and wrote 56.545 MB perf.data (~2470503 samples) ] |
@@ -182,7 +182,7 @@ mean either that the record step recorded event types that it wasn't | |||
182 | really interested in, or the script was run against a trace file that | 182 | really interested in, or the script was run against a trace file that |
183 | doesn't correspond to the script. | 183 | doesn't correspond to the script. |
184 | 184 | ||
185 | The script generated by -g option option simply prints a line for each | 185 | The script generated by -g option simply prints a line for each |
186 | event found in the trace stream i.e. it basically just dumps the event | 186 | event found in the trace stream i.e. it basically just dumps the event |
187 | and its parameter values to stdout. The print_header() function is | 187 | and its parameter values to stdout. The print_header() function is |
188 | simply a utility function used for that purpose. Let's rename the | 188 | simply a utility function used for that purpose. Let's rename the |
@@ -359,7 +359,7 @@ your script: | |||
359 | # cat kernel-source/tools/perf/scripts/python/bin/syscall-counts-record | 359 | # cat kernel-source/tools/perf/scripts/python/bin/syscall-counts-record |
360 | 360 | ||
361 | #!/bin/bash | 361 | #!/bin/bash |
362 | perf record -c 1 -f -a -M -R -e raw_syscalls:sys_enter | 362 | perf record -a -e raw_syscalls:sys_enter |
363 | ---- | 363 | ---- |
364 | 364 | ||
365 | The 'report' script is also a shell script with the same base name as | 365 | The 'report' script is also a shell script with the same base name as |
@@ -449,12 +449,10 @@ available as calls back into the perf executable (see below). | |||
449 | As an example, the following perf record command can be used to record | 449 | As an example, the following perf record command can be used to record |
450 | all sched_wakeup events in the system: | 450 | all sched_wakeup events in the system: |
451 | 451 | ||
452 | # perf record -c 1 -f -a -M -R -e sched:sched_wakeup | 452 | # perf record -a -e sched:sched_wakeup |
453 | 453 | ||
454 | Traces meant to be processed using a script should be recorded with | 454 | Traces meant to be processed using a script should be recorded with |
455 | the above options: -c 1 says to sample every event, -a to enable | 455 | the above option: -a to enable system-wide collection. |
456 | system-wide collection, -M to multiplex the output, and -R to collect | ||
457 | raw samples. | ||
458 | 456 | ||
459 | The format file for the sched_wakep event defines the following fields | 457 | The format file for the sched_wakep event defines the following fields |
460 | (see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format): | 458 | (see /sys/kernel/debug/tracing/events/sched/sched_wakeup/format): |
@@ -584,7 +582,7 @@ files: | |||
584 | 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 | 582 | 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 |
585 | 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 | 583 | 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 |
586 | 584 | ||
587 | The *autodict* function returns a special special kind of Python | 585 | The *autodict* function returns a special kind of Python |
588 | dictionary that implements Perl's 'autovivifying' hashes in Python | 586 | dictionary that implements Perl's 'autovivifying' hashes in Python |
589 | i.e. with autovivifying hashes, you can assign nested hash values | 587 | i.e. with autovivifying hashes, you can assign nested hash values |
590 | without having to go to the trouble of creating intermediate levels if | 588 | without having to go to the trouble of creating intermediate levels if |