From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jacob Pan Subject: Re: [PATCH 1/3] idle: add support for tasks that inject idle Date: Mon, 14 Nov 2016 08:20:28 -0800 Message-ID: <20161114082028.6c0ce338@jacob-builder> References: <1478718312-12847-1-git-send-email-jacob.jun.pan@linux.intel.com> <1478718312-12847-2-git-send-email-jacob.jun.pan@linux.intel.com> <20161114150119.GG3142@twins.programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from mga14.intel.com ([192.55.52.115]:54760 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932809AbcKNQSe (ORCPT ); Mon, 14 Nov 2016 11:18:34 -0500 In-Reply-To: <20161114150119.GG3142@twins.programming.kicks-ass.net> Sender: linux-pm-owner@vger.kernel.org List-Id: linux-pm@vger.kernel.org To: Peter Zijlstra Cc: LKML , Linux PM , Thomas Gleixner , Ingo Molnar , Zhang Rui , Rafael Wysocki , "Chen, Yu C" , Sebastian Andrzej Siewior , Petr Mladek , Srinivas Pandruvada , Arjan van de Ven , jacob.jun.pan@linux.intel.com On Mon, 14 Nov 2016 16:01:19 +0100 Peter Zijlstra wrote: > On Wed, Nov 09, 2016 at 11:05:10AM -0800, Jacob Pan wrote: > > +void play_idle() > > +{ > > + /* > > + * Only FIFO tasks can disable the tick since they don't > > need the forced > > + * preemption. > > + */ > > + WARN_ON_ONCE(current->policy != SCHED_FIFO); > > + WARN_ON_ONCE(current->nr_cpus_allowed != 1); > > + WARN_ON_ONCE(!(current->flags & PF_KTHREAD)); > > + WARN_ON_ONCE(!(current->flags & PF_NO_SETAFFINITY)); > > + rcu_sleep_check(); > > + > > + preempt_disable(); > > + current->flags |= PF_IDLE; > > + do_idle(); > > + current->flags &= ~PF_IDLE; > > + > > + preempt_fold_need_resched(); > > + preempt_enable(); > > +} > > +EXPORT_SYMBOL_GPL(play_idle); > > Hurm.. didn't this initially also include the setup of the timer and > take an timeout argument? right, the initial version has a timeout and init_timer_on_stack(timer); I thought since this play_idle timer is likely to expire instead of being canceled, so I switched to hrtimer by caller. We don't have an on stack hrtimer, right? or Should we consider adding one? Thanks, Jacob