From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751498AbdFHNS3 (ORCPT ); Thu, 8 Jun 2017 09:18:29 -0400 Received: from mail-pf0-f196.google.com ([209.85.192.196]:35790 "EHLO mail-pf0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751232AbdFHNS2 (ORCPT ); Thu, 8 Jun 2017 09:18:28 -0400 Date: Thu, 8 Jun 2017 23:18:13 +1000 From: Nicholas Piggin To: Peter Zijlstra Cc: Michael Ellerman , torvalds@linux-foundation.org, will.deacon@arm.com, oleg@redhat.com, paulmck@linux.vnet.ibm.com, benh@kernel.crashing.org, linux-kernel@vger.kernel.org, mingo@kernel.org, stern@rowland.harvard.edu, linuxppc-dev Subject: Re: [RFC][PATCH 5/5] powerpc: Remove SYNC from _switch Message-ID: <20170608231813.7fdac022@roar.ozlabs.ibm.com> In-Reply-To: <20170608124540.olt2rv3nbnd45pxr@hirez.programming.kicks-ass.net> References: <20170607161501.819948352@infradead.org> <20170607162013.905320602@infradead.org> <20170608103244.1b4b24c9@roar.ozlabs.ibm.com> <20170608065400.zhfao5lba6i3s7j6@hirez.programming.kicks-ass.net> <20170608172938.62b30475@roar.ozlabs.ibm.com> <20170608075720.kc2p3tybghzbmrz3@hirez.programming.kicks-ass.net> <877f0mere1.fsf@concordia.ellerman.id.au> <20170608200015.7f92965a@roar.ozlabs.ibm.com> <20170608124540.olt2rv3nbnd45pxr@hirez.programming.kicks-ass.net> Organization: IBM X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 8 Jun 2017 14:45:40 +0200 Peter Zijlstra wrote: > On Thu, Jun 08, 2017 at 08:00:15PM +1000, Nicholas Piggin wrote: > > > I have those, I just also would like one in the core scheduler's use > > of smp_mb__after_spinlock(), because it would be easy for core scheduler > > change to miss that quirk. Sure we can say that Peter and scheduler > > maintainers know about powerpc oddities, but then why shouldn't it also > > go into a comment there? > > So the core scheduler guarantees smp_mb() or equivalent full transitive > ordering happens at schedule() time. > > It has for a fairly long time and I don't think we'll ever get rid of > that, its fairly fundamental. > > PPC is special in that smp_mb() ends up being the strongest ordering > primitive there is. But note that PPC is not unique, afaict Alpha is in > the same boat. They rely on the MB from the scheduler core. > > IA64 OTOH, while they have smp_mb() == mb() still needs SYNC.I in > __switch_to() to serialize against (instruction) cache flushes. > > So while I'm all for adding comments explaining what the core provides, > I don't see immediate reasons to call out PPC. I guess I see your point... okay, will constrain the comment to powerpc context switch and primitives code. Any fundamental change to such scheduler barriers I guess would require at least a glance over arch switch code :) My plan is to send the powerpc sync removal patch for hopefully 4.13 merge. I'm pretty sure it will be equally happy with your patches. Unless you can see any problems with it? More eyes would be welcome. Thanks, Nick