From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org,
eranian@google.com, ak@linux.intel.com
Subject: Re: [PATCH] perf/x86: Consider pinned events for group validation
Date: Tue, 20 Aug 2019 16:10:14 +0200 [thread overview]
Message-ID: <20190820141014.GU2332@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1565977750-76693-1-git-send-email-kan.liang@linux.intel.com>
On Fri, Aug 16, 2019 at 10:49:10AM -0700, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> perf stat -M metrics relies on weak groups to reject unschedulable
> groups and run them as non-groups.
> This uses the group validation code in the kernel. Unfortunately
> that code doesn't take pinned events, such as the NMI watchdog, into
> account. So some groups can pass validation, but then later still
> never schedule.
But if you first create the group and then a pinned event it 'works',
which is inconsistent and makes all this timing dependent.
> @@ -2011,9 +2011,11 @@ static int validate_event(struct perf_event *event)
> */
> static int validate_group(struct perf_event *event)
> {
> + struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
> struct perf_event *leader = event->group_leader;
> struct cpu_hw_events *fake_cpuc;
> - int ret = -EINVAL, n;
> + struct perf_event *pinned_event;
> + int ret = -EINVAL, n, i;
>
> fake_cpuc = allocate_fake_cpuc();
> if (IS_ERR(fake_cpuc))
> @@ -2033,6 +2035,24 @@ static int validate_group(struct perf_event *event)
> if (n < 0)
> goto out;
>
> + /*
> + * The new group must can be scheduled
> + * together with current pinned events.
> + * Otherwise, it will never get a chance
> + * to be scheduled later.
That's wrapped short; also I don't think it is sufficient; what if you
happen to have a pinned event on CPU1 (and not others) and happen to run
validation for a new CPU1 event on CPUn ?
Also; per that same; it is broken, you're accessing the cpu-local cpuc
without serialization.
> + */
> + for (i = 0; i < cpuc->n_events; i++) {
> + pinned_event = cpuc->event_list[i];
> + if (WARN_ON_ONCE(!pinned_event))
> + continue;
> + if (!pinned_event->attr.pinned)
> + continue;
> + fake_cpuc->n_events = n;
> + n = collect_events(fake_cpuc, pinned_event, false);
> + if (n < 0)
> + goto out;
> + }
> +
> fake_cpuc->n_events = 0;
> ret = x86_pmu.schedule_events(fake_cpuc, n, NULL);
>
> --
> 2.7.4
>
next prev parent reply other threads:[~2019-08-20 14:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 17:49 [PATCH] perf/x86: Consider pinned events for group validation kan.liang
2019-08-20 14:10 ` Peter Zijlstra [this message]
2019-08-20 14:52 ` Liang, Kan
2019-08-20 15:09 ` Peter Zijlstra
2019-08-20 17:13 ` Liang, Kan
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=20190820141014.GU2332@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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