[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160615215918.GY30921@twins.programming.kicks-ass.net>
Date: Wed, 15 Jun 2016 23:59:18 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Waiman Long <waiman.long@....com>
Cc: Davidlohr Bueso <dave@...olabs.net>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
x86@...nel.org, linux-alpha@...r.kernel.org,
linux-ia64@...r.kernel.org, linux-s390@...r.kernel.org,
linux-arch@...r.kernel.org, Jason Low <jason.low2@...com>,
Dave Chinner <david@...morbit.com>,
Scott J Norton <scott.norton@....com>,
Douglas Hatch <doug.hatch@....com>
Subject: Re: [RFC PATCH-tip v2 1/6] locking/osq: Make lock/unlock proper
acquire/release barrier
On Wed, Jun 15, 2016 at 04:04:07PM -0400, Waiman Long wrote:
>
> BTW, when will the smp_acquire__after_ctrl_dep() patch goes into the tip
> tree? My patch will have a dependency on that when I make the change.
Should already be in as part of that spin_unlock_wait() fixup.
/me checks..
tip/locking/core contains:
33ac279677dc ("locking/barriers: Introduce smp_acquire__after_ctrl_dep()")
Powered by blists - more mailing lists