From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754151AbbKLSAN (ORCPT ); Thu, 12 Nov 2015 13:00:13 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:45787 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753734AbbKLSAK (ORCPT ); Thu, 12 Nov 2015 13:00:10 -0500 Date: Thu, 12 Nov 2015 19:00:03 +0100 From: Peter Zijlstra To: David Daney Cc: ralf@linux-mips.org, linux-kernel@vger.kernel.org, Paul McKenney , Will Deacon , torvalds@linux-foundation.org, boqun.feng@gmail.com Subject: Re: [RFC][PATCH] mips: Fix arch_spin_unlock() Message-ID: <20151112180003.GE17308@twins.programming.kicks-ass.net> References: <20151112123123.GZ17308@twins.programming.kicks-ass.net> <5644D08D.4080206@caviumnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5644D08D.4080206@caviumnetworks.com> 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 On Thu, Nov 12, 2015 at 09:46:53AM -0800, David Daney wrote: > For CONFIG_CPU_CAVIUM_OCTEON the proper thing would be: > > smp_wmb(); > smp_rmb(); > > Which expands to exactly the same thing as wmb() because smp_rmb() expands > to nothing. OK, so the current code isn't broken because for Cavium wmb is suffient because rmb is a no-op, and for !Cavium wmb expands to SYNC. > You yourself seem to have added smp_store_release(), so we could even do: > > smp_store_release(&lock->h.serving_now, lock->h.serving_now + 1); > > That would leave us to cook up a proper definition of smp_store_release(). That is indeed the better solution.