From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH v2 1/2] sched: let the scheduler see CPU idle states Date: Fri, 19 Sep 2014 01:17:15 +0200 Message-ID: <20140918231715.GO2848@worktop.localdomain> References: <1409844730-12273-1-git-send-email-nicolas.pitre@linaro.org> <1409844730-12273-2-git-send-email-nicolas.pitre@linaro.org> <20140918173733.GQ4723@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Nicolas Pitre Cc: "Paul E. McKenney" , Ingo Molnar , Daniel Lezcano , "Rafael J. Wysocki" , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linaro-kernel@lists.linaro.org List-Id: linux-pm@vger.kernel.org On Thu, Sep 18, 2014 at 02:32:25PM -0400, Nicolas Pitre wrote: > On Thu, 18 Sep 2014, Paul E. McKenney wrote: > > So what is it that you really need to do here? > > In short, we don't want the cpufreq data to go away (see the 2 scenarios > above) while the scheduler is looking at it. The scheduler uses the > provided accessors (see patch 2/2) so we can put any protection > mechanism we want in them. A simple spinlock could do just as well > which should be good enough. rq->lock disables interrupts so on that something like kick_all_cpus_sync() will guarantee what you need -- wake_up_all_idle_cpus() will not.