linux-kernel - Re: [PATCH] tracing: hwlat: update old comment

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20170214150512.2f0b376e@gandalf.local.home>
Date:   Tue, 14 Feb 2017 15:05:12 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Luiz Capitulino <lcapitulino@...hat.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing: hwlat: update old comment

On Mon, 13 Feb 2017 12:25:17 -0500
Luiz Capitulino <lcapitulino@...hat.com> wrote:

> The ftrace hwlat does support a cpumask.
> 
> Signed-off-by: Luiz Capitulino <lcapitulino@...hat.com>

Thanks! Applied.

-- Steve

> ---
>  kernel/trace/trace_hwlat.c | 5 +----
>  1 file changed, 1 insertion(+), 4 deletions(-)
> 
> diff --git a/kernel/trace/trace_hwlat.c b/kernel/trace/trace_hwlat.c
> index af344a1b..1199fe1 100644
> --- a/kernel/trace/trace_hwlat.c
> +++ b/kernel/trace/trace_hwlat.c
> @@ -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)
>  {