linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "Liang, Kan" <kan.liang@intel.com>,
	Ingo Molnar <mingo@redhat.com>, Jiri Olsa <jolsa@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Yao Jin <yao.jin@linux.intel.com>,
	Kan Liang <kan.liang@linux.intel.com>
Subject: Re: [PATCH] perf stat: Add Topdown metrics L2 events as default events
Date: Fri, 9 Jul 2021 09:52:03 -0300	[thread overview]
Message-ID: <YOhGc+81IjLKRXVS@kernel.org> (raw)
In-Reply-To: <CAM9d7ciuJFpFJC+DSdSg=3VeK_YUgSiWdTE++LZHk4ir6NGLtg@mail.gmail.com>

Em Thu, Jul 08, 2021 at 10:31:34PM -0700, Namhyung Kim escreveu:
> On Thu, Jul 8, 2021 at 9:04 AM <kan.liang@intel.com> wrote:
> > With the patch:

> >  $ perf stat sleep 1

> >  Performance counter stats for 'sleep 1':

> >               0.59 msec task-clock                #    0.001 CPUs utilized
> >                  1      context-switches          #    1.687 K/sec
> >                  0      cpu-migrations            #    0.000 /sec
> >                 76      page-faults               #  128.198 K/sec
> >          1,405,318      cycles                    #    2.371 GHz
> >          1,471,136      instructions              #    1.05  insn per cycle
> >            310,132      branches                  #  523.136 M/sec
> >             10,435      branch-misses             #    3.36% of all branches
> >          8,431,908      slots                     #   14.223 G/sec
> >          1,554,116      topdown-retiring          #     18.4% retiring
> >          1,289,585      topdown-bad-spec          #     15.2% bad speculation
> >          2,810,636      topdown-fe-bound          #     33.2% frontend bound
> >          2,810,636      topdown-be-bound          #     33.2% backend bound
> >            231,464      topdown-heavy-ops         #      2.7% heavy operations       #     15.6% light operations
> >          1,223,453      topdown-br-mispredict     #     14.5% branch mispredict      #      0.8% machine clears
> >          1,884,779      topdown-fetch-lat         #     22.3% fetch latency          #     10.9% fetch bandwidth
> >          1,454,917      topdown-mem-bound         #     17.2% memory bound           #     16.0% Core bound

> >        1.001179699 seconds time elapsed

> >        0.000000000 seconds user
> >        0.001238000 seconds sys

> > Reviewed-by: Andi Kleen <ak@linux.intel.com>
> > Signed-off-by: Kan Liang <kan.liang@linux.intel.com>

> Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks, applied.

- Arnaldo


      reply	other threads:[~2021-07-09 12:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08 16:02 [PATCH] perf stat: Add Topdown metrics L2 events as default events kan.liang
2021-07-09  5:31 ` Namhyung Kim
2021-07-09 12:52   ` 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=YOhGc+81IjLKRXVS@kernel.org \
    --to=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=yao.jin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).