From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>,
Joakim Zhang <qiangqing.zhang@nxp.com>,
Andi Kleen <ak@linux.intel.com>,
lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH] perf stat: Fix duration_time value for higher intervals
Date: Mon, 18 May 2020 17:48:48 +0200 [thread overview]
Message-ID: <20200518154848.GA11620@krava> (raw)
In-Reply-To: <20200518152351.GD24211@kernel.org>
On Mon, May 18, 2020 at 12:23:51PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, May 18, 2020 at 03:14:45PM +0200, Jiri Olsa escreveu:
> > Joakim reported wrong duration_time value for interval bigger
> > than 4000 [1].
> >
> > The problem is in the interval value we pass to update_stats
> > function, which is typed as 'unsigned int' and overflows when
> > we get over 2^32 (happens between intervals 4000 and 5000).
> >
> > Retyping the passed value to unsigned long long.
>
> Thanks, applied and added this:
>
> Fixes: b90f1333ef08 ("perf stat: Update walltime_nsecs_stats in interval mode")
>
> Ok?
yep, thanks
jirka
>
> - Arnaldo
>
> > [1] https://www.spinics.net/lists/linux-perf-users/msg11777.html
> >
> > Reported-by: Joakim Zhang <qiangqing.zhang@nxp.com>
> > Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> > ---
> > tools/perf/builtin-stat.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/tools/perf/builtin-stat.c b/tools/perf/builtin-stat.c
> > index e0c1ad23c768..4deb2d46a343 100644
> > --- a/tools/perf/builtin-stat.c
> > +++ b/tools/perf/builtin-stat.c
> > @@ -367,7 +367,7 @@ static void process_interval(void)
> > }
> >
> > init_stats(&walltime_nsecs_stats);
> > - update_stats(&walltime_nsecs_stats, stat_config.interval * 1000000);
> > + update_stats(&walltime_nsecs_stats, stat_config.interval * 1000000ULL);
> > print_counters(&rs, 0, NULL);
> > }
> >
> > --
> > 2.25.4
> >
>
> --
>
> - Arnaldo
>
prev parent reply other threads:[~2020-05-18 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 13:14 [PATCH] perf stat: Fix duration_time value for higher intervals Jiri Olsa
2020-05-18 15:23 ` Arnaldo Carvalho de Melo
2020-05-18 15:48 ` Jiri Olsa [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=20200518154848.GA11620@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.org \
--cc=qiangqing.zhang@nxp.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