Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Namhyung Kim" <namhyung@kernel.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH] perf stat: Fix aggregation of cgroup events
Date: Fri, 02 Oct 2026 09:14:30 +0000	[thread overview]
Message-ID: <20261002091431.3089A1F00893@smtp.kernel.org> (raw)
In-Reply-To: <20261002054832.64980-1-namhyung@kernel.org>

> I got a report that perf stat with BPF and cgroup is broken with
> aggregation like per-socket or node.  On my machine, running the
> following command shows the problem.
> 
>   $ sudo perf stat -a --bpf-counters --per-socket -e cycles \
>     --for-each-cgroup /user.slice,/system.slice  sleep 1
> 
>    Performance counter stats for 'system wide':
> 
>   S0       12      <not counted>      cpu_atom/cycles/                 user.slice
>   S0       16      <not counted>      cpu_core/cycles/                 user.slice
>   S0       12      <not counted>      cpu_atom/cycles/                 system.slice
>   S0       16      <not counted>      cpu_core/cycles/                 system.slice
> 
>          1.002798147 seconds time elapsed
> [ ... ]
> 
>          1.003231856 seconds time elapsed
> 
> Reported-by: Chun-Tse Shao <ctshao@google.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261002054832.64980-1-namhyung@kernel.org?part=1


  reply	other threads:[~2026-10-02  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  5:48 [PATCH] perf stat: Fix aggregation of cgroup events Namhyung Kim
2026-10-02  9:14 ` sashiko-bot [this message]
2026-10-02 17:13 ` Chun-Tse Shao

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=20261002091431.3089A1F00893@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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