From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [RFC/RFT][PATCH 1/7] time: tick-sched: Reorganize idle tick management code Date: Mon, 5 Mar 2018 11:44:46 +0100 Message-ID: <20180305104446.GN25201@hirez.programming.kicks-ass.net> References: <1657351.s4RTvEoqBQ@aspire.rjw.lan> <46071692.o1R0bjyNQV@aspire.rjw.lan> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <46071692.o1R0bjyNQV@aspire.rjw.lan> Sender: linux-kernel-owner@vger.kernel.org To: "Rafael J. Wysocki" Cc: Thomas Gleixner , Frederic Weisbecker , Paul McKenney , Thomas Ilsche , Doug Smythies , Rik van Riel , Aubrey Li , Mike Galbraith , LKML , Linux PM List-Id: linux-pm@vger.kernel.org On Sun, Mar 04, 2018 at 11:24:00PM +0100, Rafael J. Wysocki wrote: > +/** > + * tick_nohz_idle_prepare - prepare for entering idle on the current CPU. > + * > + * Called when we start the idle loop. > + */ > +void tick_nohz_idle_prepare(void) > +{ > + __tick_nohz_idle_prepare(); > + > + local_irq_enable(); > +} I really dislike the asymmetry in IRQ state you introduced here. __tick_nohz_idle_prepare() disables IRQs. Must we do that?