[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20211025103657.1c30a2c0@gandalf.local.home>
Date: Mon, 25 Oct 2021 10:36:57 -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 Mon, 25 Oct 2021 10:08:39 +0200
Daniel Bristot de Oliveira <bristot@...nel.org> wrote:
> osnoise and timerlat tracers share a lot of code, including the osnoise: events.
>
> However, the osnoise: events have different behavior depending on which tracer
> is enabled. So, while this patch allows the same tracer to run in multiple
> instances (e.g., two instances running osnoise), it still does not allow
> instances of timerlat and osnoise in parallel (e.g., one timerlat and osnoise).
>
> Should I add the text above to the log?
Yes please.
-- Steve
Powered by blists - more mailing lists