[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADDUTFzG4mvTyN4cBLzqkGBWkPkDP1-jzOZKxosxP+X8rKLBew@mail.gmail.com>
Date: Sun, 3 Aug 2025 14:08:14 +0300
From: Costa Shulyupin <costa.shul@...hat.com>
To: Tomas Glozar <tglozar@...hat.com>
Cc: Steven Rostedt <rostedt@...dmis.org>, linux-trace-kernel@...r.kernel.org,
linux-kernel@...r.kernel.org, John Kacur <jkacur@...hat.com>,
Luis Goncalves <lgoncalv@...hat.com>, Arnaldo Carvalho de Melo <acme@...nel.org>, Chang Yin <cyin@...hat.com>
Subject: Re: [PATCH 2/8] rtla/timerlat: Add action on threshold feature
On Wed, 11 Jun 2025 at 16:57, Tomas Glozar <tglozar@...hat.com> wrote:
> A new option, -A/--on-threshold, is added, taking an argument
The term "threshold" is ambiguous. The use of the term is inconsistent
across the tools. In osnoise top and hist, it means "the minimum delta
to be considered noise," which conflicts with the semantics of the
`--on-threshold <action>` option. To avoid confusion, I propose
introducing "low" and "high" thresholds and updating the sources and
documentation accordingly.
Thanks
Costa
Powered by blists - more mailing lists