From: Song Liu <songliubraving@fb.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>,
"Ian Rogers" <irogers@google.com>
Subject: Re: [PATCH v3] perf/core: Set event shadow time for inactive events too
Date: Mon, 6 Dec 2021 23:11:34 +0000 [thread overview]
Message-ID: <A629A4F4-1BA4-4DCF-B4F0-F0E80B55738A@fb.com> (raw)
In-Reply-To: <20211205224843.1503081-1-namhyung@kernel.org>
> On Dec 5, 2021, at 2:48 PM, Namhyung Kim <namhyung@kernel.org> wrote:
>
> While commit f79256532682 ("perf/core: fix userpage->time_enabled of
> inactive events") fixed this problem for user rdpmc usage, bperf (perf
> stat with BPF) still has the same problem that accessing inactive perf
> events from BPF using bpf_perf_event_read_value().
>
> You can reproduce this problem easily. As this is about a small
> window with multiplexing, we need a large number of events and short
> duration like below:
>
> # perf stat -a -v --bpf-counters -e instructions,branches,branch-misses \
> -e cache-references,cache-misses,bus-cycles,ref-cycles,cycles sleep 0.1
>
> Control descriptor is not initialized
> instructions: 19616489 431324015 360374366
> branches: 3685346 417640114 344175443
> branch-misses: 75714 404089360 336145421
> cache-references: 438667 390474289 327444074
> cache-misses: 49279 349333164 272835067
> bus-cycles: 631887 283423953 165164214
> ref-cycles: 2578771111104847872 18446744069443110306 182116355
> cycles: 1785221016051271680 18446744071682768912 115821694
>
> Performance counter stats for 'system wide':
>
> 19,616,489 instructions # 0.00 insn per cycle ( 83.55%)
> 3,685,346 branches ( 82.41%)
> 75,714 branch-misses # 2.05% of all branches ( 83.19%)
> 438,667 cache-references ( 83.86%)
> 49,279 cache-misses # 11.234 % of all cache refs ( 78.10%)
> 631,887 bus-cycles ( 58.27%)
> 2,578,771,111,104,847,872 ref-cycles (0.00%)
> 1,785,221,016,051,271,680 cycles (0.00%)
>
> 0.010824702 seconds time elapsed
>
> As you can see, it shows invalid values for the last two events.
> The -v option shows that the enabled time is way bigger than the
> running time. So it scaled the counter values using the ratio
> between the two and resulted in that. This problem can get worse
> if users want no-aggregation or cgroup aggregation with a small
> interval.
>
> Actually 18446744069443110306 is 0xffffffff01b345a2 so it seems to
> have a negative enabled time. In fact, bperf keeps values returned by
> bpf_perf_event_read_value() which calls perf_event_read_local(), and
> accumulates delta between two calls. When event->shadow_ctx_time is
> not set, it'd return invalid enabled time which is bigger than normal.
> Later, the shadow time is set and the function starts to return a
> valid time. At the moment, the recent value is smaller than before so
> the delta in the bperf can be negative.
>
> I think we need to set the shadow time even the events are inactive so
> that BPF programs (or other potential users) can see valid time values
> anytime.
>
> Cc: Song Liu <songliubraving@fb.com>
> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Acked-by: Song Liu <song@kernel.org>
next prev parent reply other threads:[~2021-12-06 23:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 22:48 [PATCH v3] perf/core: Set event shadow time for inactive events too Namhyung Kim
2021-12-06 23:11 ` Song Liu [this message]
2021-12-08 23:22 ` Peter Zijlstra
2021-12-09 5:52 ` Namhyung Kim
2021-12-09 8:21 ` Peter Zijlstra
2021-12-09 11:26 ` Peter Zijlstra
2021-12-09 11:34 ` Peter Zijlstra
2021-12-09 21:51 ` Namhyung Kim
2021-12-10 10:19 ` Peter Zijlstra
2021-12-10 18:59 ` Namhyung Kim
2021-12-20 9:39 ` Peter Zijlstra
2021-12-09 21:35 ` Namhyung Kim
2021-12-10 10:33 ` Peter Zijlstra
2021-12-10 23:19 ` Namhyung Kim
2021-12-17 16:35 ` Peter Zijlstra
2021-12-18 9:09 ` Song Liu
2021-12-20 9:30 ` Peter Zijlstra
2021-12-20 9:54 ` Peter Zijlstra
2021-12-21 12:39 ` Peter Zijlstra
2021-12-20 12:19 ` Peter Zijlstra
2021-12-21 5:54 ` Namhyung Kim
2021-12-21 7:23 ` Song Liu
2021-12-21 11:21 ` Peter Zijlstra
2022-01-18 11:17 ` [tip: perf/urgent] perf: Fix perf_event_read_local() time tip-bot2 for Peter Zijlstra
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=A629A4F4-1BA4-4DCF-B4F0-F0E80B55738A@fb.com \
--to=songliubraving@fb.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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 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).