tracing/hwlat: Update old comment about migration

Luiz Capitulino · rostedt · commit 8e0f11429aec · 2017-02-15T09:02:25.000-05:00
The ftrace hwlat does support a cpumask. Link: http://lkml.kernel.org/r/20170213122517.6e211955@redhat.com Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
diff --git a/kernel/trace/trace_hwlat.c b/kernel/trace/trace_hwlat.c
@@ -322,10 +322,7 @@ static void move_to_next_cpu(void)
  * 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)
 {

Original file line number	Diff line number	Diff line change
`@@ -322,10 +322,7 @@ static void move_to_next_cpu(void)`
`322`	`322`	`* need to ensure nothing else might be running (and thus preempting).`
`323`	`323`	`* Obviously this should never be used in production environments.`
`324`	`324`	`*`
`325`		`- * Currently this runs on which ever CPU it was scheduled on, but most`
`326`		`- * real-world hardware latency situations occur across several CPUs,`
`327`		`- * but we might later generalize this if we find there are any actualy`
`328`		`- * systems with alternate SMI delivery or other hardware latencies.`
	`325`	`+ * Executes one loop interaction on each CPU in tracing_cpumask sysfs file.`
`329`	`326`	`*/`
`330`	`327`	`static int kthread_fn(void *data)`
`331`	`328`	`{`