linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Crystal Wood <crwood@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-trace-kernel@vger.kernel.org,
	 John Kacur <jkacur@redhat.com>,
	Costa Shulyupin <costa.shul@redhat.com>
Subject: Re: [PATCH 2/7] tools/rtla: Move top/hist union members elsewhere
Date: Tue, 26 Aug 2025 14:42:23 -0500	[thread overview]
Message-ID: <b14451e2823743c5f884c862edbf4954991cf629.camel@redhat.com> (raw)
In-Reply-To: <CAP4=nvQtKguNDikon2idnaET=Rpfsuo2DQeoRD4Nn8_FFRUX=A@mail.gmail.com>

On Tue, 2025-08-26 at 15:58 +0200, Tomas Glozar wrote:
> čt 21. 8. 2025 v 5:58 odesílatel Crystal Wood <crwood@redhat.com> napsal:
> > 
> > The hist members were very similar between timerlat and top, so
> > just use one common hist struct.
> > 
> > output_divisor, quiet, and pretty printing are pretty generic
> > concepts that can go in the main struct even if not every
> > specific tool (currently) uses them.
> > 
> 
> Absolutely. Quiet and pretty printing are currently only used for top,
> but they might make sense for hist, too, in the future. output_divisor
> is actually always set to 1000 for osnoise-hist, once -n/--nano is
> implemented for osnoise, it will also be used by both osnoise-hist and
> osnoise-top, just like with rtla-timerlat.
> 
> For the commit message, maybe "Move hist/top-specific params into
> common struct" would work better? "Elsewhere" doesn't quite capture
> the idea for me.

OK.

> 
> > diff --git a/tools/tracing/rtla/src/osnoise_top.c b/tools/tracing/rtla/src/osnoise_top.c
> > index ad5daa8210aa..7c68feed300e 100644
> > --- a/tools/tracing/rtla/src/osnoise_top.c
> > +++ b/tools/tracing/rtla/src/osnoise_top.c
> > @@ -125,11 +125,12 @@ static void osnoise_top_header(struct osnoise_tool *top)
> >  {
> >         struct osnoise_params *params = top->params;
> >         struct trace_seq *s = top->trace.seq;
> 
> > +       bool pretty = params->common.pretty_output;
> 
> Is there any specific motivation for doing this and not just using
> params->common.pretty_output directly, like for the other parameters?

Because that wouldn't be pretty :-)

(it just felt like it was repeated enough to be worth it)

-Crystal


  reply	other threads:[~2025-08-26 19:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21  3:57 [PATCH 0/7] tools/rtla: Code consolidation and osnoise actions Crystal Wood
2025-08-21  3:57 ` [PATCH 1/7] tools/rtla: Consolidate common parameters into shared structure Crystal Wood
2025-08-26 14:15   ` Tomas Glozar
2025-08-21  3:57 ` [PATCH 2/7] tools/rtla: Move top/hist union members elsewhere Crystal Wood
2025-08-26 13:58   ` Tomas Glozar
2025-08-26 19:42     ` Crystal Wood [this message]
2025-08-27 12:55       ` Tomas Glozar
2025-08-26 18:05   ` Costa Shulyupin
2025-08-26 20:39     ` Crystal Wood
2025-08-27  6:51     ` Tomas Glozar
2025-08-21  3:57 ` [PATCH 3/7] tools/rtla: Create common_apply_config() Crystal Wood
2025-08-27 11:33   ` Tomas Glozar
2025-08-29 20:35     ` Crystal Wood
2025-08-21  3:57 ` [PATCH 4/7] tools/rtla: Consolidate code between osnoise/timerlat and hist/top Crystal Wood
2025-08-27 13:34   ` Tomas Glozar
2025-08-29 20:46     ` Crystal Wood
2025-08-21  3:57 ` [PATCH 5/7] tools/rtla: Fix -A option name in test comment Crystal Wood
2025-08-28  6:52   ` Tomas Glozar
2025-08-21  3:57 ` [PATCH 6/7] tools/rtla: Add test engine support for unexpected output Crystal Wood
2025-08-28  8:09   ` Tomas Glozar
2025-08-29 21:34     ` Crystal Wood
2025-09-01 12:50       ` Tomas Glozar
2025-09-02 19:08         ` Crystal Wood
2025-09-03 16:15           ` Tomas Glozar
2025-08-21  3:57 ` [PATCH 7/7] tools/rtla: Add remaining support for osnoise actions Crystal Wood
2025-08-28 10:57   ` Tomas Glozar
2025-08-29 21:47     ` Crystal Wood

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=b14451e2823743c5f884c862edbf4954991cf629.camel@redhat.com \
    --to=crwood@redhat.com \
    --cc=costa.shul@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglozar@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).