All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf test: waiting.sh: Replace timestamp polling with sleep
Date: Tue, 8 Sep 2026 18:06:50 -0300	[thread overview]
Message-ID: <aqB46q7p5I_3G3DO@x2> (raw)
In-Reply-To: <CAP-5=fUY9H-26_CAE6yLXr9ci6F4Wia3BsFJjeDqbPo1qcO7Eg@mail.gmail.com>

On Tue, Sep 08, 2026 at 10:14:29AM -0700, Ian Rogers wrote:
> On Tue, Sep 8, 2026 at 8:21 AM Adrian Hunter <adrian.hunter@intel.com> wrote:
> >
> > The waiting helpers implement timeouts using:
> >
> >   date +%s%1N
> >
> > This relies on GNU coreutils date truncating %N to the specified width,
> > so %1N yields tenths of a second.
> >
> > Rust coreutils (uutils) interprets the width differently and does not
> > truncate the nanoseconds field.  Consequently "date +%1N" returns all
> > nine nanosecond digits, causing the elapsed-time calculation to be done
> > in nanoseconds while timeout values remain in tenths of a second.
> >
> > As a result, timeout comparisons succeed immediately and the waiting
> > helpers time out on their first iteration.  This causes
> > test_intel_pt.sh to fail on systems using uutils "date".
> >
> > Avoid implementation-specific date formatting entirely.  Instead, wait
> > for 100 ms on each iteration and count the timeout down.  Besides fixing
> > the portability issue, this removes the busy-waiting behaviour in
> > wait_for_perf_to_start(), which could otherwise consume CPU while
> > waiting for perf record to start.
> >
> > Since the timeout is now based on repeated sleeps, it is only
> > approximate.  Update the comments accordingly.  Also make is_running()
> > wait for exactly the documented number of tenths by changing its timeout
> > test from -gt to the new logic, and quote tm_out in the modified code.
> >
> > Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
> 
> Reviewed-by: Ian Rogers <irogers@google.com>

Thanks, applied to perf-tools-next, for v7.4.

- Arnaldo

      reply	other threads:[~2026-09-08 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 15:20 [PATCH] perf test: waiting.sh: Replace timestamp polling with sleep Adrian Hunter
2026-09-08 15:27 ` sashiko-bot
2026-09-08 17:14 ` Ian Rogers
2026-09-08 21:06   ` Arnaldo Carvalho de Melo [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=aqB46q7p5I_3G3DO@x2 \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    /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.