All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: linux-perf-users@vger.kernel.org
Cc: irogers@google.com, acme@kernel.org, namhyung@kernel.org
Subject: duration_time regression
Date: Tue, 1 Aug 2023 13:32:13 -0700	[thread overview]
Message-ID: <ZMlrzcVrVi1lTDmn@tassilo> (raw)


With recent perf duration_time output regressed:

e.g. with an older version I get duration_time only once:

% perf stat -e cycles,duration_time true

CPU0                 190,925      cycles
... all the other CPUs printing cycles
CPU0                5,047,008 ns   duration_time

       0.005047008 seconds time elapsed

     
with the current perf it is printed on all CPUs, but not counted on most
of them:

% perf stat -e cycles,duration_time true

# started on Tue Aug  1 13:29:26 2023

 Performance counter stats for 'system wide':

CPU0               61,301      cycles                                                                
... print cycles for all CPUS ...
CPU0            5,343,556 ns   duration_time                                                         
CPU1        <not counted> ns   duration_time                                                         
CPU2        <not counted> ns   duration_time                                                         
CPU3        <not counted> ns   duration_time                                                         
CPU4        <not counted> ns   duration_time                                                         
... repeat the same for all CPUs ...

which is fairly useless.

-Andi

             reply	other threads:[~2023-08-01 20:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 20:32 Andi Kleen [this message]
2023-08-01 21:47 ` duration_time regression Ian Rogers

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=ZMlrzcVrVi1lTDmn@tassilo \
    --to=ak@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=irogers@google.com \
    --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.