[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170922093329.wizest62uolktwc7@hirez.programming.kicks-ass.net>
Date: Fri, 22 Sep 2017 11:33:29 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Andy Lutomirski <luto@...nel.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Will Deacon <will.deacon@....com>,
Alan Stern <stern@...land.harvard.edu>,
Michael Ellerman <mpe@...erman.id.au>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-arch <linux-arch@...r.kernel.org>,
Dave Watson <davejwatson@...com>,
maged michael <maged.michael@...il.com>
Subject: Re: Rough notes from sys_membarrier() lightning BoF
On Thu, Sep 21, 2017 at 10:23:39AM -0700, James Bottomley wrote:
> We have one system that locks up if
> multiple CPUs have outstanding coherency operations on the private bus,
> but that's only one annoying CPU (which we manage with a special lock
> inside the PA-RISC mmu code).
Hehe, yeah. I saw that code recently and had a WTF moment ;-)
Powered by blists - more mailing lists