Commit 8e0f1142 authored by Luiz Capitulino's avatar Luiz Capitulino Committed by Steven Rostedt (VMware)

tracing/hwlat: Update old comment about migration

The ftrace hwlat does support a cpumask.

Link: http://lkml.kernel.org/r/20170213122517.6e211955@redhat.comSigned-off-by: default avatarLuiz Capitulino <lcapitulino@redhat.com>
Signed-off-by: default avatarSteven Rostedt (VMware) <rostedt@goodmis.org>
parent 8a58a34b
...@@ -322,10 +322,7 @@ static void move_to_next_cpu(void) ...@@ -322,10 +322,7 @@ static void move_to_next_cpu(void)
* need to ensure nothing else might be running (and thus preempting). * need to ensure nothing else might be running (and thus preempting).
* Obviously this should never be used in production environments. * Obviously this should never be used in production environments.
* *
* Currently this runs on which ever CPU it was scheduled on, but most * Executes one loop interaction on each CPU in tracing_cpumask sysfs file.
* 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.
*/ */
static int kthread_fn(void *data) static int kthread_fn(void *data)
{ {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment