tracing: hwlat: update old comment
Subsystems (2)
PATCH 1/1 tracing: hwlat: update old comment
The ftrace hwlat does support a cpumask.
Signed-off-by Luiz Capitulino <[email protected]>
--- kernel/trace/trace_hwlat.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
kernel/trace/trace_hwlat.c +1 -4
@@ -322,10 +322,7 @@ static void move_to_next_cpu(bool initmask)* need to ensure nothing else might be running (and thus preempting). * Obviously this should never be used in production environments. * -* Currently this runs on which ever CPU it was scheduled on, but most -* real-world hardware latency situations occur across several CPUs, -* but we might later generalize this if we find there are any actualy -* systems with alternate SMI delivery or other hardware latencies. +* Executes one loop interaction on each CPU in tracing_cpumask sysfs file. */ static int kthread_fn (void *data) {
Signature · 1 line
2.5.5
Quoted 3 lines · On Mon, 13 Feb 2017 12:25:17 -0500 Luiz Capitulino <[email protected]>…
The ftrace hwlat does support a cpumask.
Signed-off-by Luiz Capitulino <[email protected]>
Thanks! Applied.
-- Steve
Quoted 20 lines
--- kernel/trace/trace_hwlat.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)kernel/trace/trace_hwlat.c +1
-4@@ -322,10 +322,7 @@ static void move_to_next_cpu(bool initmask)* need to ensure nothing else might be running (and thus preempting). * Obviously this should never be used in production environments. * -* Currently this runs on which ever CPU it was scheduled on, but most -* real-world hardware latency situations occur across several CPUs, -* but we might later generalize this if we find there are any actualy -* systems with alternate SMI delivery or other hardware latencies. +* Executes one loop interaction on each CPU in tracing_cpumask sysfs file. */ static int kthread_fn (void *data) {