All of lore.kernel.org
 help / color / mirror / Atom feed
From: nicolassaenzj@gmail.com
To: Peter Xu <peterx@redhat.com>
Cc: linux-rt-users@vger.kernel.org, williams@redhat.com, jkacur@redhat.com
Subject: Re: [PATCH 2/2] oslat: Add trace maker prior starting main thread
Date: Mon, 12 Jul 2021 12:17:40 +0200	[thread overview]
Message-ID: <1a630437ca66263d8adf41e11d357514f902cdb4.camel@gmail.com> (raw)
In-Reply-To: <YOiX+lp/PQL136TZ@t490s>

[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]

Hi Peter,

On Fri, 2021-07-09 at 14:39 -0400, Peter Xu wrote:
> On Fri, Jul 09, 2021 at 05:54:14PM +0200, Nicolas Saenz Julienne wrote:
> > After a long tracing session it's sometimes hard to find the moment
> > oslat started. So leave a message in the trace buffer just before the
> > main thread starts.
> > 
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzju@redhat.com>
> > ---
> >  src/oslat/oslat.c | 4 ++++
> >  1 file changed, 4 insertions(+)
> > 
> > diff --git a/src/oslat/oslat.c b/src/oslat/oslat.c
> > index d35be57..20bf02b 100644
> > --- a/src/oslat/oslat.c
> > +++ b/src/oslat/oslat.c
> > @@ -400,6 +400,10 @@ static void *thread_main(void *arg)
> >  	while (g.n_threads_running != g.n_threads)
> >  		relax();
> >  
> > +	if (!g.preheat)
> > +		tracemark(false, "%s: Starting thread on CPU %d.\n",
> > +			  g.app_name, t->core_i);
> > +
> >  	frc(&t->frc_start);
> >  	doit(t);
> >  	frc(&t->frc_stop);
> > -- 
> > 2.31.1
> > 
> 
> Not sure how it would help.. but no objection either. :)

For example, I tend to enable all trace points on Isolated CPUs. It's
manageable, since once oslat runs you shouldn't be getting much action. But you
get 10s/100s MBs of noise generated while oslat is being initialized. This
makes finding the beginning of the test very annoying and time consuming.

> Acked-by: Peter Xu <peterx@redhat.com>

Thanks!

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      reply	other threads:[~2021-07-12 10:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-09 15:54 [PATCH 1/2] rt-utils: Add option to avoid stopping tracing in tracemark() Nicolas Saenz Julienne
2021-07-09 15:54 ` [PATCH 2/2] oslat: Add trace maker prior starting main thread Nicolas Saenz Julienne
2021-07-09 18:39   ` Peter Xu
2021-07-12 10:17     ` nicolassaenzj [this message]

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=1a630437ca66263d8adf41e11d357514f902cdb4.camel@gmail.com \
    --to=nicolassaenzj@gmail.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterx@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.