From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>
Subject: Re: perf: odd event scheduling issue
Date: Wed, 20 May 2015 17:25:34 +0200 [thread overview]
Message-ID: <20150520152534.GJ18673@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150520135209.GI18673@twins.programming.kicks-ass.net>
On Wed, May 20, 2015 at 03:52:09PM +0200, Peter Zijlstra wrote:
> >
> > This patch limits the number of counters available to each CPU when
> > the HT bug workaround is enabled.
> >
> > This is necessary to avoid situation of counter starvation. Such can
> > arise from configuration where one HT thread, HT0, is using all 4 counters
> > with corrupting events which require exclusion the the sibling HT, HT1.
> >
>
> OK, so if you have the watchdog enabled, that's 1 event, and having a
> max of 2 GP events, adding another 2 events is fail.
Hmm, so we count all events, including those scheduled on fixed purpose
counters.
Lemme see if I can cure that.
next prev parent reply other threads:[~2015-05-20 15:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 3:07 perf: odd event scheduling issue Vince Weaver
2015-05-20 7:00 ` Peter Zijlstra
2015-05-20 7:11 ` Jiri Olsa
2015-05-20 9:28 ` Peter Zijlstra
2015-05-20 13:52 ` Peter Zijlstra
2015-05-20 15:25 ` Peter Zijlstra [this message]
2015-05-20 16:08 ` Peter Zijlstra
2015-05-20 16:28 ` Peter Zijlstra
2015-05-20 23:10 ` Andi Kleen
2015-05-21 12:04 ` Stephane Eranian
2015-05-20 16:25 ` Jiri Olsa
2015-05-21 12:05 ` Stephane Eranian
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=20150520152534.GJ18673@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=vincent.weaver@maine.edu \
/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