[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210607114718.5f8d6c38@oasis.local.home>
Date: Mon, 7 Jun 2021 11:47:18 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Daniel Bristot de Oliveira <bristot@...hat.com>
Cc: linux-kernel@...r.kernel.org, Phil Auld <pauld@...hat.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Kate Carcia <kcarcia@...hat.com>,
Jonathan Corbet <corbet@....net>,
Ingo Molnar <mingo@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>,
Alexandre Chartre <alexandre.chartre@...cle.com>,
Clark Willaims <williams@...hat.com>,
John Kacur <jkacur@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>, linux-doc@...r.kernel.org
Subject: Re: [PATCH V3 8/9] tracing: Add osnoise tracer
On Mon, 7 Jun 2021 14:00:56 +0200
Daniel Bristot de Oliveira <bristot@...hat.com> wrote:
> I am using these more "generic terms" because they are also used by the timerlat
> tracer.
>
> In the timerlat tracer, the "in" file is used to stop the tracer for a given IRQ
> latency (so, the "inside" operation), while the "out" is used to stop the tracer
> in the thread latency (hence the outside operation).
>
> The total sounds good for the "out"! But the single does not work fine for the
> IRQ... how about: stop_tracing_partial_us ?
>
> It is hard to find a good shared name :-/
What about:
stop_tracing_us and stop_tracing_total_us, and not have anything
special for the first one?
-- Steve
Powered by blists - more mailing lists