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  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:   Fri, 22 Oct 2021 22:47:11 -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 V4 05/19] trace/osnoise: Allow multiple instances of the
 same tracer

On Thu, 21 Oct 2021 14:56:43 +0200
Daniel Bristot de Oliveira <> wrote:

> Allow more than one instance of the same tracer. The workload will
> start when the first trace_array (instance) is registered and will
> stop when the last instance is unregistered.

> Osnoise and timerlat are still mutually exclusive because of the
> different behavior of the osnoise: tracepoints.

I don't understand what the above means, or how it is relative to this

-- Steve

Powered by blists - more mailing lists