From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from bombadil.infradead.org ([198.137.202.9]:34894 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751092AbcBLULF (ORCPT ); Fri, 12 Feb 2016 15:11:05 -0500 Date: Fri, 12 Feb 2016 21:10:11 +0100 From: Peter Zijlstra To: Josh Poimboeuf Cc: Jiri Slaby , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, Michal Marek , Andy Lutomirski , Borislav Petkov , Linus Torvalds , Andi Kleen , Pedro Alves , Namhyung Kim , Bernd Petrovitsch , Chris J Arges , Andrew Morton , Arnaldo Carvalho de Melo , David Vrabel , Borislav Petkov , Konrad Rzeszutek Wilk , Boris Ostrovsky , Jeremy Fitzhardinge , Chris Wright , Alok Kataria , Rusty Russell , Herbert Xu , "David S. Miller" , Pavel Machek , "Rafael J. Wysocki" , Len Brown , Matt Fleming , Alexei Starovoitov , netdev@vger.kernel.org, Ananth N Mavinakayanahalli , Anil S Keshavamurthy , Masami Hiramatsu , Gleb Natapov , Paolo Bonzini , kvm@vger.kernel.org, Wim Van Sebroeck , Guenter Roeck , linux-watchdog@vger.kernel.org, Waiman Long Subject: Re: [PATCH 00/33] Compile-time stack metadata validation Message-ID: <20160212201011.GW6357@twins.programming.kicks-ass.net> References: <56BDB5A8.9030006@suse.cz> <20160212144543.GA29004@treble.redhat.com> <20160212171037.GV6357@twins.programming.kicks-ass.net> <20160212183206.GB29004@treble.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160212183206.GB29004@treble.redhat.com> Sender: linux-watchdog-owner@vger.kernel.org List-Id: linux-watchdog@vger.kernel.org On Fri, Feb 12, 2016 at 12:32:06PM -0600, Josh Poimboeuf wrote: > What I actually see in the listing is: > > decl __percpu_prefix:__preempt_count > je 1f: > .... > 1: > call ___preempt_schedule > > So it puts the "call ___preempt_schedule" in the slow path. Ah yes indeed. Same difference though. > I also don't see how that would be related to the use of the asm > statement in the __preempt_schedule() macro. Doesn't the use of > unlikely() in preempt_enable() put the call in the slow path? Sadly no, unlikely() and asm_goto don't work well together. But the slow path or not isn't the reason we do the asm call thing. > #define preempt_enable() \ > do { \ > barrier(); \ > if (unlikely(preempt_count_dec_and_test())) \ > preempt_schedule(); \ > } while (0) > > Also, why is the thunk needed? Any reason why preempt_enable() can't be > called directly from C? That would make the call-site save registers and increase the size of every preempt_enable(). By using the thunk we can do callee saved registers and avoid blowing up the call site.