linux-kernel - Re: [PATCH V4 05/19] trace/osnoise: Allow multiple instances of the same tracer

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211022224711.7d1cbddf@rorschach.local.home>
Date:   Fri, 22 Oct 2021 22:47:11 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Daniel Bristot de Oliveira <bristot@...nel.org>
Cc:     Ingo Molnar <mingo@...hat.com>, Tom Zanussi <zanussi@...nel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Juri Lelli <juri.lelli@...hat.com>,
        Clark Williams <williams@...hat.com>,
        John Kacur <jkacur@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        linux-rt-users@...r.kernel.org, linux-trace-devel@...r.kernel.org,
        linux-kernel@...r.kernel.org
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 <bristot@...nel.org> 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
commit?

-- Steve