Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753599AbcCaHgx (ORCPT ); Thu, 31 Mar 2016 03:36:53 -0400 Received: from bombadil.infradead.org ([198.137.202.9]:43416 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750972AbcCaHgw (ORCPT ); Thu, 31 Mar 2016 03:36:52 -0400 Date: Thu, 31 Mar 2016 09:36:42 +0200 From: Peter Zijlstra To: Petros Koutoupis Cc: Mike Galbraith , linux-kernel@vger.kernel.org, "Paul E. McKenney" , Thomas Gleixner , Davidlohr Bueso , Linus Torvalds , catalin.marinas@arm.com, "H. Peter Anvin" Subject: Re: futex: clarification needed with drop_futex_key_refs and memory barriers Message-ID: <20160331073642.GE3408@twins.programming.kicks-ass.net> References: <1459007812.5648.5.camel@petros-ultrathin> <1459059948.3799.14.camel@gmail.com> <20160329095039.GE3408@twins.programming.kicks-ass.net> <1459388710.4600.7.camel@petros-ultrathin> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1459388710.4600.7.camel@petros-ultrathin> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 938 Lines: 23 On Wed, Mar 30, 2016 at 08:45:10PM -0500, Petros Koutoupis wrote: > > But this is not a correctness (nor ordering) issue; but purely an > > architectural side-effect. Furthermore; some proposed changes: > > > > http://marc.info/?l=linux-kernel&m=145400059704564&w=2 > > > > might change this side-effect. > > > > Has there been an update to this patch? The last I see, the conversation > ended at the end of January, and there hasn't been a change in the > mainline. Peter Anvin was going to look at this with some of the Intel hardware people to fully explore the ramifications of this change, we're waiting on feedback from that. > >> Your adjustments here make complete sense. Are you preparing it for > submission in the near future? I'll think about it, adding the extra barrier for decrement is of course not really nice if not strictly required. And while it will not impact x86 the weakly ordered archs will be affected.