public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	alexander.shishkin@linux.intel.com, namhyung@kernel.org,
	yao.jin@linux.intel.com, linux-kernel@vger.kernel.org,
	yuzhoujian@didichuxing.com, tmricht@linux.vnet.ibm.com,
	anton@samba.org
Subject: Re: [PATCH] perf stat: Fix shadow stats for clock events
Date: Tue, 27 Nov 2018 09:37:41 -0300	[thread overview]
Message-ID: <20181127123741.GA15747@kernel.org> (raw)
In-Reply-To: <2f319b94-8d6c-581b-19f3-43a1ab5774ef@linux.ibm.com>

Em Tue, Nov 27, 2018 at 01:50:44PM +0530, Ravi Bangoria escreveu:
> 
> 
> On 11/16/18 7:05 PM, Jiri Olsa wrote:
> > On Fri, Nov 16, 2018 at 09:58:43AM +0530, Ravi Bangoria wrote:
> >> Commit 0aa802a79469 ("perf stat: Get rid of extra clock display
> >> function") introduced scale and unit for clock events. Thus,
> >> perf_stat__update_shadow_stats() now saves scaled values of
> >> clock events in msecs, instead of original nsecs. But while
> >> calculating values of shadow stats we still consider clock
> >> event values in nsecs. This results in a wrong shadow stat
> >> values. Ex,
> >>
> >>   # ./perf stat -e task-clock,cycles ls
> >>     <SNIP>
> >>               2.60 msec task-clock:u    #    0.877 CPUs utilized
> >>          2,430,564      cycles:u        # 1215282.000 GHz
> >>
> >> Fix this by saving original nsec values for clock events in
> >> perf_stat__update_shadow_stats(). After patch:
> >>
> >>   # ./perf stat -e task-clock,cycles ls
> >>     <SNIP>
> >>               3.14 msec task-clock:u    #    0.839 CPUs utilized
> >>          3,094,528      cycles:u        #    0.985 GHz
> >>
> >> Reported-by: Anton Blanchard <anton@samba.org>
> >> Suggested-by: Jiri Olsa <jolsa@redhat.com>
> >> Fixes: 0aa802a79469 ("perf stat: Get rid of extra clock display function")
> >> Signed-off-by: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
> > 
> > Reviewed-by: Jiri Olsa <jolsa@kernel.org>
> 
> Hi Arnaldo, Please pull this.

I did it yesterday, its just that I installed a new notebook and the
MTA was down :-\ All should be fixed by now and the patch should go
Ingo's way soon.

- Arnaldo

  reply	other threads:[~2018-11-27 12:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15  9:55 [PATCH 1/2] perf stat: Use perf_evsel__is_clocki() for clock events Ravi Bangoria
2018-11-15  9:55 ` [RFC 2/2] perf stat: Fix shadow stats " Ravi Bangoria
2018-11-15 14:17   ` Jiri Olsa
2018-11-16  4:28     ` [PATCH] " Ravi Bangoria
2018-11-16 13:35       ` Jiri Olsa
2018-11-26 18:45         ` Arnaldo Carvalho de Melo
2018-11-27  8:20         ` Ravi Bangoria
2018-11-27 12:37           ` Arnaldo Carvalho de Melo [this message]
2018-12-14 20:19       ` [tip:perf/core] " tip-bot for Ravi Bangoria
2018-12-18 13:46       ` tip-bot for Ravi Bangoria
2018-11-15 13:55 ` [PATCH 1/2] perf stat: Use perf_evsel__is_clocki() " Jiri Olsa
2018-11-15 19:22   ` Arnaldo Carvalho de Melo
2018-11-22  7:13 ` [tip:perf/core] " tip-bot for Ravi Bangoria

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=20181127123741.GA15747@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anton@samba.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=tmricht@linux.vnet.ibm.com \
    --cc=yao.jin@linux.intel.com \
    --cc=yuzhoujian@didichuxing.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