From 6e13c0aac620ec418f1a47f6a3bb9230a6677e3f Mon Sep 17 00:00:00 2001 From: Cheng-Han Wu Date: Sun, 3 May 2026 18:14:27 +0800 Subject: [PATCH] docs: admin-guide: fix stress-ng command examples The workload tracing guide includes stress-ng command examples with a stray "command." word at the end. This makes the examples invalid if they are copied and run directly. Remove the stray word from the stress-ng example. Also use "--" in the perf record example to clearly separate perf record options from the workload command being recorded. Signed-off-by: Cheng-Han Wu Reviewed-by: Shuah Khan Signed-off-by: Jonathan Corbet Message-ID: <20260503101429.254394-3-hank20010209@gmail.com> --- Documentation/admin-guide/workload-tracing.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/admin-guide/workload-tracing.rst b/Documentation/admin-guide/workload-tracing.rst index 22cb05025ffc..43a3c8098654 100644 --- a/Documentation/admin-guide/workload-tracing.rst +++ b/Documentation/admin-guide/workload-tracing.rst @@ -271,7 +271,7 @@ exercised: The following command runs the stressor:: - stress-ng --netdev 1 -t 60 --metrics command. + stress-ng --netdev 1 -t 60 --metrics We can use the perf record command to record the events and information associated with a process. This command records the profiling data in the @@ -281,7 +281,7 @@ Using the following commands you can record the events associated with the netdev stressor, view the generated report perf.data and annotate the output to view the statistics of each instruction of the program:: - perf record stress-ng --netdev 1 -t 60 --metrics command. + perf record -- stress-ng --netdev 1 -t 60 --metrics perf report perf annotate