From: John Kacur <jkacur@redhat.com>
To: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
Cc: Daniel Bristot de Oliveira <bristot@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Clark Williams <williams@redhat.com>,
linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtla/osnoise: Better report when histogram is empty
Date: Wed, 12 Jun 2024 10:12:26 -0400 (EDT) [thread overview]
Message-ID: <9d283173-4ff6-fbac-bcc3-e712daa99572@redhat.com> (raw)
In-Reply-To: <Zml6JmH5cbS7-HfZ@uudg.org>
On Wed, 12 Jun 2024, Luis Claudio R. Goncalves wrote:
> When osnoise hist does not observe any samples above the threshold,
> no entries are recorded and the final report shows empty entries
> for the usual statistics (count, min, max, avg):
>
> [~]# osnoise hist -d 5s -T 500
> # RTLA osnoise histogram
> # Time unit is microseconds (us)
> # Duration: 0 00:00:05
> Index
> over:
> count:
> min:
> avg:
> max:
>
> That could lead users to confusing interpretations of the results.
>
> A simple solution is to report 0 for count and the statistics, making it
> clear that no noise (above the defined threshold) was observed:
>
> [~]# osnoise hist -d 5s -T 500
> # RTLA osnoise histogram
> # Time unit is microseconds (us)
> # Duration: 0 00:00:05
> Index
> over: 0
> count: 0
> min: 0
> avg: 0
> max: 0
>
>
> Signed-off-by: Luis Claudio R. Goncalves <lgoncalv@redhat.com>
> ---
> tools/tracing/rtla/src/osnoise_hist.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/tools/tracing/rtla/src/osnoise_hist.c b/tools/tracing/rtla/src/osnoise_hist.c
> index 7be17d09f7e85..214e2c93fde01 100644
> --- a/tools/tracing/rtla/src/osnoise_hist.c
> +++ b/tools/tracing/rtla/src/osnoise_hist.c
> @@ -374,6 +374,7 @@ osnoise_print_stats(struct osnoise_hist_params *params, struct osnoise_tool *too
> {
> struct osnoise_hist_data *data = tool->data;
> struct trace_instance *trace = &tool->trace;
> + int has_samples = 0;
> int bucket, cpu;
> int total;
>
> @@ -402,11 +403,25 @@ osnoise_print_stats(struct osnoise_hist_params *params, struct osnoise_tool *too
> continue;
> }
>
> + /* There are samples above the threshold */
IMHO The comment isn't needed because the variable had_samples is
descriptive, but it's not a big deal either
> + has_samples = 1;
> trace_seq_printf(trace->seq, "\n");
> trace_seq_do_printf(trace->seq);
> trace_seq_reset(trace->seq);
> }
>
> + /*
> + * If no samples were recorded, skip calculations, print zeroed statistics
> + * and return.
> + */
> + if (!has_samples) {
> + trace_seq_reset(trace->seq);
> + trace_seq_printf(trace->seq, "over: 0\ncount: 0\nmin: 0\navg: 0\nmax: 0\n");
> + trace_seq_do_printf(trace->seq);
> + trace_seq_reset(trace->seq);
> + return;
> + }
> +
> if (!params->no_index)
> trace_seq_printf(trace->seq, "over: ");
>
>
>
>
Reviewed-by: John Kacur <jkacur@redhat.com>
next prev parent reply other threads:[~2024-06-12 14:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 10:36 [PATCH] rtla/osnoise: Better report when histogram is empty Luis Claudio R. Goncalves
2024-06-12 14:12 ` John Kacur [this message]
2024-06-21 8:26 ` Daniel Bristot de Oliveira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9d283173-4ff6-fbac-bcc3-e712daa99572@redhat.com \
--to=jkacur@redhat.com \
--cc=bristot@kernel.org \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).