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] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 25 Oct 2021 21:08:43 -0400
From:   Steven Rostedt <>
To:     Daniel Bristot de Oliveira <>
Cc:     Ingo Molnar <>, Tom Zanussi <>,
        Masami Hiramatsu <>,
        Juri Lelli <>,
        Clark Williams <>,
        John Kacur <>,
        Peter Zijlstra <>,
        Thomas Gleixner <>,
        Sebastian Andrzej Siewior <>,,,
Subject: Re: [PATCH V5 04/20] trace/osnoise: Use
 start/stop_per_cpu_kthreads() on osnoise_cpus_write()

On Mon, 25 Oct 2021 19:40:29 +0200
Daniel Bristot de Oliveira <> wrote:

> When writing a new CPU mask via osnoise/cpus, if the tracer is running,
> the workload is restarted to follow the new cpumask. The restart is
> currently done using osnoise_workload_start/stop(), which disables the
> workload *and* the instrumentation. However, disabling the
> instrumentation is not necessary.
> Calling start/stop_per_cpu_kthreads() is enough to apply the new
> osnoise/cpus config.
> No functional change.

I nuked the "No functional change.". You can't have the changes of the
above and say there wasn't functional changes, as the first paragraph
explains the functional changes.

-- Steve

Powered by blists - more mailing lists