Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752115AbdGLRqz (ORCPT ); Wed, 12 Jul 2017 13:46:55 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:32895 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751041AbdGLRqy (ORCPT ); Wed, 12 Jul 2017 13:46:54 -0400 Date: Wed, 12 Jul 2017 19:46:42 +0200 From: Peter Zijlstra To: "Paul E. McKenney" Cc: Frederic Weisbecker , Christoph Lameter , "Li, Aubrey" , Andi Kleen , Aubrey Li , tglx@linutronix.de, len.brown@intel.com, rjw@rjwysocki.net, tim.c.chen@linux.intel.com, arjan@linux.intel.com, yang.zhang.wz@gmail.com, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods Message-ID: <20170712174642.sewe3vlryq7bm7kc@hirez.programming.kicks-ass.net> References: <20170710144609.GD31832@tassilo.jf.intel.com> <20170710164206.5aon5kelbisxqyxq@hirez.programming.kicks-ass.net> <20170710172705.GA3441@tassilo.jf.intel.com> <20170711094157.5xcwkloxnjehieqv@hirez.programming.kicks-ass.net> <20170711160926.GA18805@lerouge> <20170711163422.etydkhhtgfthpfi5@hirez.programming.kicks-ass.net> <20170711180931.GP2393@linux.vnet.ibm.com> <20170712115451.xxz3jkau7ape76n5@hirez.programming.kicks-ass.net> <20170712155651.GX2393@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170712155651.GX2393@linux.vnet.ibm.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 524 Lines: 11 On Wed, Jul 12, 2017 at 08:56:51AM -0700, Paul E. McKenney wrote: > Very good, I have queued the patch below. I left out the removal of > the export as I need to work out why the export was there. If it turns > out not to be needed, I will remove the related ones as well. 'git grep rcu_idle_enter' shows no callers other than kernel/sched/idle.c. Which seems a clear indication its not needed. You also have to ask yourself, do I want joe module author to ever call this. To which I suspect the answer is: hell no ;-)