From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754106AbcBBWiU (ORCPT ); Tue, 2 Feb 2016 17:38:20 -0500 Received: from e31.co.us.ibm.com ([32.97.110.149]:60404 "EHLO e31.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753285AbcBBWiQ (ORCPT ); Tue, 2 Feb 2016 17:38:16 -0500 X-IBM-Helo: d03dlp02.boulder.ibm.com X-IBM-MailFrom: paulmck@linux.vnet.ibm.com X-IBM-RcptTo: linux-kernel@vger.kernel.org Date: Tue, 2 Feb 2016 14:38:10 -0800 From: "Paul E. McKenney" To: Peter Zijlstra Cc: Boqun Feng , Will Deacon , "Maciej W. Rozycki" , David Daney , =?iso-8859-1?Q?M=E5ns_Rullg=E5rd?= , Ralf Baechle , linux-kernel@vger.kernel.org, torvalds@linux-foundation.org Subject: Re: [RFC][PATCH] mips: Fix arch_spin_unlock() Message-ID: <20160202223810.GN6719@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20160127233836.GQ4503@linux.vnet.ibm.com> <20160128095718.GC30928@arm.com> <20160128223131.GV4503@linux.vnet.ibm.com> <20160129095958.GA4541@arm.com> <20160129102253.GG4503@linux.vnet.ibm.com> <20160201135621.GD6828@arm.com> <20160202035458.GF6719@linux.vnet.ibm.com> <20160202051904.GC1239@fixme-laptop.cn.ibm.com> <20160202064433.GG6719@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-MML: disable X-Content-Scanned: Fidelis XPS MAILER x-cbid: 16020222-8236-0000-0000-000015C13C86 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Feb 02, 2016 at 06:23:37PM +0100, Peter Zijlstra wrote: > > > On 2 February 2016 07:44:33 CET, "Paul E. McKenney" wrote: > > > > >> If so, do we also need to take the following pairing into > >consideration? > >> > >> o smp_store_release() -> READ_ONCE(); if ;smp_rmb(); > > > We rely on this with smp_cond_aquire() to extend the chain. We do indeed! And it is not possible to use smp_load_acquire() given this API becauseof the "!". Hmmm... If this one turns out to be problematic, there are some ways of dealing with it. But thank you for reminding me of it. I think, anyway. ;-) Thanx, Paul