diff options
| author | Luiz Capitulino <lcapitulino@redhat.com> | 2017-02-13 12:25:17 -0500 |
|---|---|---|
| committer | Steven Rostedt (VMware) <rostedt@goodmis.org> | 2017-02-15 09:02:25 -0500 |
| commit | 8e0f11429aec1119b17cbfcfa2d3194c8e864a26 (patch) | |
| tree | b217f7ab6536659cd466a37c1756a8cf31dbc9a9 | |
| parent | 8a58a34ba479d42b3ef28f8ffd9e245a81a7786f (diff) | |
tracing/hwlat: Update old comment about migration
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>
| -rw-r--r-- | kernel/trace/trace_hwlat.c | 5 |
1 files changed, 1 insertions, 4 deletions
diff --git a/kernel/trace/trace_hwlat.c b/kernel/trace/trace_hwlat.c index 775569ec50d0..bf209d2657ab 100644 --- 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) { |