From: Michael Petlan <mpetlan@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: acme@redhat.com, vmolnaro@redhat.com, linux-perf-users@vger.kernel.org
Subject: Re: perf test fail :: "perf stat --bpf-counters --for-each-cgroup test"
Date: Tue, 23 Jul 2024 11:36:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.LRH.2.20.2407231136060.11376@Diego> (raw)
In-Reply-To: <CAM9d7cjxnz_MEqSN6EsfrMejhQwGro9yjHoWrnDrugnNWuGipA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
On Fri, 19 Jul 2024, Namhyung Kim wrote:
> Hello,
>
> On Fri, Jul 19, 2024 at 2:50 AM Michael Petlan <mpetlan@redhat.com> wrote:
> >
> > Hello Namhyung,
> >
> > we were investigating some test failures of the testcase mentioned
> > in $subj. We have narrowed it down to:
> >
> > # perf stat -C 0,1 --for-each-cgroup system.slice,user.slice -e cycles -- taskset -c 1 perf test -w thloop
> >
> > Performance counter stats for 'CPU(s) 0,1':
> > <not counted> cycles system.slice
> > 3,020,401,084 cycles user.slice
> >
> > 1.009787097 seconds time elapsed
> >
> > As seen, the system.slice is not counted properly in our case. It
> > happens even without bpf-counters being involved.
> >
> > There were rumours that it might be caused due to too small system
> > load, but it apparently happens even when the load was replaced by
> > "thloop" workload from perf-test's workload library. However, even
> > so, if the load was insufficient, we'd see a value – 0 instead of
> > "not counted". The "<not counted>" result is printed if the counter
> > wasn't properly enabled and running.
> >
> > Have you encountered this problem? What could cause it?
>
> Sometimes, it depends on the system activity.
> I assumed there would be some system operation running
> on the given CPUs at any time. If not, it can fail..
Thanks for response. However, in such case, I'd expect "0" value instead
of "<not counted>". As far as I understand, "<not supported>" occurs when
an event cannot be even opened, "<not counted>" appears when the event
can be opened, but for example there aren't enough free hardware counters,
so it does not run any counting actually. But for cases when there is not
enough load, we get simply low numerical values, or 0, don't we...
Michael
>
> Thanks,
> Namhyung
>
>
prev parent reply other threads:[~2024-07-23 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 9:50 perf test fail :: "perf stat --bpf-counters --for-each-cgroup test" Michael Petlan
[not found] ` <CA+JHD90TkDVHPw4jqxMX2guqsg-8xrqD2iiEfZ_akixvVYZKZg@mail.gmail.com>
2024-07-19 11:05 ` Michael Petlan
2024-11-01 10:15 ` Michael Petlan
2024-11-04 19:52 ` Namhyung Kim
2024-07-20 0:30 ` Namhyung Kim
2024-07-23 9:36 ` Michael Petlan [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=alpine.LRH.2.20.2407231136060.11376@Diego \
--to=mpetlan@redhat.com \
--cc=acme@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=vmolnaro@redhat.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).