From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: multiplexing broken on amd fam16h?
Date: Wed, 22 Jul 2015 22:10:17 +0200 [thread overview]
Message-ID: <20150722201017.GZ25159@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.1507221558450.1341@vincent-weaver-1.umelst.maine.edu>
On Wed, Jul 22, 2015 at 03:59:28PM -0400, Vince Weaver wrote:
> On Wed, 22 Jul 2015, Peter Zijlstra wrote:
>
> > On Wed, Jul 22, 2015 at 12:56:23PM -0400, Vince Weaver wrote:
> > > yes, with this applied the check_multiplex test passes.
> >
> > Awesome, I'll try and write up a proper patch later tonight.
>
> I'm just curious, it seems like sort of a generic fix, is there a reaon I
> was only hitting the bug on AMD fam16h?
Not that I can think of.. maybe just consistently lucky on timings :/
>From what I can tell of the thing it _should_ fail on pretty much
everything.
next prev parent reply other threads:[~2015-07-22 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 18:14 Vince Weaver
2015-07-21 19:32 ` Peter Zijlstra
2015-07-21 20:08 ` Vince Weaver
2015-07-22 12:22 ` Peter Zijlstra
2015-07-22 14:57 ` Vince Weaver
2015-07-22 15:00 ` Peter Zijlstra
2015-07-22 15:02 ` Vince Weaver
2015-07-22 15:06 ` Peter Zijlstra
2015-07-22 15:41 ` Peter Zijlstra
2015-07-22 16:56 ` Vince Weaver
2015-07-22 19:07 ` Peter Zijlstra
2015-07-22 19:59 ` Vince Weaver
2015-07-22 20:10 ` Peter Zijlstra [this message]
2015-07-21 22:10 ` Peter Zijlstra
2015-07-22 14:10 ` Peter Zijlstra
2015-07-22 14:36 ` Vince Weaver
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=20150722201017.GZ25159@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
Powered by JetHome