From: Leo Yan <leo.yan@linaro.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org,
Sumanth Korikkar <sumanthk@linux.ibm.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Kevin Nomura <nomurak@google.com>
Subject: Re: [PATCH] perf stat: Do not delay the workload with --delay
Date: Thu, 15 Dec 2022 09:43:55 +0800 [thread overview]
Message-ID: <Y5p723KMYBI2W6vs@leoy-yangtze.lan> (raw)
In-Reply-To: <20221212230820.901382-1-namhyung@kernel.org>
On Mon, Dec 12, 2022 at 03:08:20PM -0800, Namhyung Kim wrote:
> The -D/--delay option is to delay the measure after the program starts.
> But the current code goes to sleep before starting the program so the
> program is delayed too. This is not the intention, let's fix it.
>
> Before:
>
> $ time sudo ./perf stat -a -e cycles -D 3000 sleep 4
> Events disabled
> Events enabled
>
> Performance counter stats for 'system wide':
>
> 4,326,949,337 cycles
>
> 4.007494118 seconds time elapsed
>
> real 0m7.474s
> user 0m0.356s
> sys 0m0.120s
>
> It ran the workload for 4 seconds and gave the 3 second delay. So it
> should skip the first 3 second and measure the last 1 second only. But
> as you can see, it delays 3 seconds and ran the workload after that for
> 4 seconds. So the total time (real) was 7 seconds.
>
> After:
>
> $ time sudo ./perf stat -a -e cycles -D 3000 sleep 4
> Events disabled
> Events enabled
>
> Performance counter stats for 'system wide':
>
> 1,063,551,013 cycles
>
> 1.002769510 seconds time elapsed
>
> real 0m4.484s
> user 0m0.385s
> sys 0m0.086s
>
> The bug was introduced when it changed enablement of system-wide events
> with a command line workload. But it should've considered the initial
> delay case. The code was reworked since then (in bb8bc52e7578) so I'm
> afraid it won't be applied cleanly.
>
> Fixes: d0a0a511493d ("perf stat: Fix forked applications enablement of counters")
> Cc: Sumanth Korikkar <sumanthk@linux.ibm.com>
> Cc: Thomas Richter <tmricht@linux.ibm.com>
> Reported-by: Kevin Nomura <nomurak@google.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Reviewed-by: Leo Yan <leo.yan@linaro.org>
prev parent reply other threads:[~2022-12-15 1:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 23:08 [PATCH] perf stat: Do not delay the workload with --delay Namhyung Kim
2022-12-13 13:13 ` Thomas Richter
2022-12-13 13:39 ` James Clark
2022-12-14 0:18 ` Ian Rogers
2022-12-14 14:41 ` Arnaldo Carvalho de Melo
2022-12-15 1:43 ` Leo Yan [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=Y5p723KMYBI2W6vs@leoy-yangtze.lan \
--to=leo.yan@linaro.org \
--cc=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=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=nomurak@google.com \
--cc=peterz@infradead.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.ibm.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.