perf docs: Fix typos
Ian Rogers
reviewerPATCH 1/1 perf docs: Fix typos
Assorted typo fixes.
Signed-off-by Ian Rogers <[email protected]>
--- tools/perf/Documentation/perf-kwork.txt | 4 ++-- tools/perf/Documentation/perf-mem.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)
tools/perf/Documentation/perf-kwork.txt +2 -2
@@ -1,4 +1,4 @@ -perf-kowrk(1) +perf-kwork(1) ============= NAME
@@ -35,7 +35,7 @@ There are several variants of 'perf kwork': perf kwork top perf kwork top -b - By default it shows the individual work events such as irq, workqeueu, + By default it shows the individual work events such as irq, workqueue, including the run time and delay (time between raise and actually entry): Runtime start Runtime end Cpu Kwork name Runtime Delaytime
tools/perf/Documentation/perf-mem.txt +1 -1
@@ -21,7 +21,7 @@ and stores are sampled. Use the -t option to limit to loads or stores. Note that on Intel systems the memory latency reported is the use-latency, not the pure load (or store latency). Use latency includes any pipeline -queueing delays in addition to the memory subsystem latency. +queuing delays in addition to the memory subsystem latency. On Arm64 this uses SPE to sample load and store operations, therefore hardware and kernel support is required. See linkperf:perf-arm-spe[1] for a setup guide.
tools/perf/Documentation/perf-record.txt +1 -1
@@ -311,7 +311,7 @@ OPTIONS User can change the size by passing the size after comma like "--call-graph dwarf,4096". - When "fp" recording is used, perf tries to save stack enties + When "fp" recording is used, perf tries to save stack entries up to the number specified in sysctl.kernel.perf_event_max_stack by default. User can change the number by passing it after comma like "--call-graph fp,32".
Signature · 1 line
2.45.1.288.g0e0cd299f1-goog
Quoted 3 lines · Ian Rogers
Assorted typo fixes.
Signed-off-by Ian Rogers <[email protected]>
Reviewed-by James Clark <[email protected]>
Quoted 51 lines
--- tools/perf/Documentation/perf-kwork.txt | 4 ++-- tools/perf/Documentation/perf-mem.txt | 2 +- tools/perf/Documentation/perf-record.txt | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-)tools/perf/Documentation/perf-kwork.txt +2
-2@@ -1,4 +1,4 @@ -perf-kowrk(1) +perf-kwork(1) ============= NAME@@ -35,7 +35,7 @@ There are several variants of 'perf kwork': perf kwork top perf kwork top -b - By default it shows the individual work events such as irq, workqeueu, + By default it shows the individual work events such as irq, workqueue, including the run time and delay (time between raise and actually entry): Runtime start Runtime end Cpu Kwork name Runtime Delaytimetools/perf/Documentation/perf-mem.txt +1
-1@@ -21,7 +21,7 @@ and stores are sampled. Use the -t option to limit to loads or stores. Note that on Intel systems the memory latency reported is the use-latency, not the pure load (or store latency). Use latency includes any pipeline -queueing delays in addition to the memory subsystem latency. +queuing delays in addition to the memory subsystem latency. On Arm64 this uses SPE to sample load and store operations, therefore hardware and kernel support is required. See linkperf:perf-arm-spe[1] for a setup guide.tools/perf/Documentation/perf-record.txt +1
-1@@ -311,7 +311,7 @@ OPTIONS User can change the size by passing the size after comma like "--call-graph dwarf,4096". - When "fp" recording is used, perf tries to save stack enties + When "fp" recording is used, perf tries to save stack entries up to the number specified in sysctl.kernel.perf_event_max_stack by default. User can change the number by passing it after comma like "--call-graph fp,32".
Quoted 3 lines · Ian Rogers
Assorted typo fixes.
Applied to perf-tools-next, thanks!
Best regards,
Signature · 1 line
Namhyung Kim <[email protected]>