From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [IPv6:2401:3900:2:1::2]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 3wnn0v61npzDqLs for ; Wed, 14 Jun 2017 23:05:03 +1000 (AEST) From: Michael Ellerman To: Nicholas Piggin Cc: linuxppc-dev@lists.ozlabs.org, "Gautham R . Shenoy" Subject: Re: [PATCH 09/13] powerpc/64s: cpuidle set polling before enabling irqs In-Reply-To: <20170614215042.45dced67@roar.ozlabs.ibm.com> References: <20170613130557.26315-1-npiggin@gmail.com> <20170613130557.26315-10-npiggin@gmail.com> <87efum3igr.fsf@concordia.ellerman.id.au> <20170614215042.45dced67@roar.ozlabs.ibm.com> Date: Wed, 14 Jun 2017 23:05:00 +1000 Message-ID: <878tkupvnn.fsf@concordia.ellerman.id.au> MIME-Version: 1.0 Content-Type: text/plain List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Nicholas Piggin writes: > On Wed, 14 Jun 2017 21:40:52 +1000 > Michael Ellerman wrote: > >> Nicholas Piggin writes: >> >> > local_irq_enable can cause interrupts to be taken which could >> > take significant amount of processing time. The idle process >> > should set its polling flag before this, so another process that >> > wakes it during this time will not have to send an IPI. >> > >> > Expand the TIF_POLLING_NRFLAG coverage to as large as possible. >> > >> > Reviewed-by: Gautham R. Shenoy >> > Signed-off-by: Nicholas Piggin >> > --- >> > drivers/cpuidle/cpuidle-powernv.c | 4 +++- >> > drivers/cpuidle/cpuidle-pseries.c | 3 ++- >> > 2 files changed, 5 insertions(+), 2 deletions(-) >> >> I don't think the cpuidle folks are really interested in these changes, >> but we should Cc them to be polite. >> >> Can you resend patches 9, 10, 11 with a subject like: >> >> "cpuidle: powernv: Set polling ..." >> >> And Cc the cpuidle folks: >> >> $ ./scripts/get_maintainer.pl -f drivers/cpuidle >> rjw@rjwysocki.net >> daniel.lezcano@linaro.org >> linux-pm@vger.kernel.org >> linux-kernel@vger.kernel.org > > Yeah I can do that. I'll send them as thier own series. They don't > depend on any of the patches in this series, so I should have done > that in the first place. Great thanks. cheers