From: Peter Zijlstra <peterz@infradead.org>
To: Song Liu <songliubraving@fb.com>
Cc: linux-kernel@vger.kernel.org, kernel-team@fb.com,
stable@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2] perf/core: fix corner case in perf_rotate_context()
Date: Tue, 8 Oct 2019 21:18:13 +0200 [thread overview]
Message-ID: <20191008191813.GG2328@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20191008165949.920548-1-songliubraving@fb.com>
On Tue, Oct 08, 2019 at 09:59:49AM -0700, Song Liu wrote:
> In perf_rotate_context(), when the first cpu flexible event fail to
> schedule, cpu_rotate is 1, while cpu_event is NULL. Since cpu_event is
> NULL, perf_rotate_context will _NOT_ call cpu_ctx_sched_out(), thus
> cpuctx->ctx.is_active will have EVENT_FLEXIBLE set. Then, the next
> perf_event_sched_in() will skip all cpu flexible events because of the
> EVENT_FLEXIBLE bit.
>
> In the next call of perf_rotate_context(), cpu_rotate stays 1, and
> cpu_event stays NULL, so this process repeats. The end result is, flexible
> events on this cpu will not be scheduled (until another event being added
> to the cpuctx).
>
> Here is an easy repro of this issue. On Intel CPUs, where ref-cycles
> could only use one counter, run one pinned event for ref-cycles, one
> flexible event for ref-cycles, and one flexible event for cycles. The
> flexible ref-cycles is never scheduled, which is expected. However,
> because of this issue, the cycles event is never scheduled either.
>
> perf stat -e ref-cycles:D,ref-cycles,cycles -C 5 -I 1000
> time counts unit events
> 1.000152973 15,412,480 ref-cycles:D
> 1.000152973 <not counted> ref-cycles (0.00%)
> 1.000152973 <not counted> cycles (0.00%)
> 2.000486957 18,263,120 ref-cycles:D
> 2.000486957 <not counted> ref-cycles (0.00%)
> 2.000486957 <not counted> cycles (0.00%)
>
> To fix this, when the flexible_active list is empty, try rotate the
> first event in the flexible_groups. Also, rename ctx_first_active() to
> ctx_event_to_rotate(), which is more accurate.
>
> Fixes: 8d5bce0c37fa ("perf/core: Optimize perf_rotate_context() event scheduling")
> Cc: stable@vger.kernel.org # v4.17+
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Arnaldo Carvalho de Melo <acme@kernel.org>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Sasha Levin <sashal@kernel.org>
> Signed-off-by: Song Liu <songliubraving@fb.com>
Thanks!
next prev parent reply other threads:[~2019-10-08 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 16:59 Song Liu
2019-10-08 19:18 ` Peter Zijlstra [this message]
2019-10-09 12:59 ` [tip: perf/urgent] perf/core: Fix " tip-bot2 for Song Liu
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=20191008191813.GG2328@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=songliubraving@fb.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®