Re: [PATCH] cpuidle:powernv: Add the CPUIDLE_FLAG_POLLING for snooze

2018-07-04 Thread Michael Ellerman
Gautham R Shenoy writes: > On Tue, Jul 03, 2018 at 07:36:16PM +0530, Vaidyanathan Srinivasan wrote: >> * Gautham R Shenoy [2018-07-03 10:54:16]: >> >> > From: "Gautham R. Shenoy" >> > >> > In the situations where snooze is the only cpuidle state due to >> > firmware not exposing any platform i

Re: [PATCH] cpuidle:powernv: Add the CPUIDLE_FLAG_POLLING for snooze

2018-07-03 Thread Gautham R Shenoy
On Tue, Jul 03, 2018 at 07:36:16PM +0530, Vaidyanathan Srinivasan wrote: > * Gautham R Shenoy [2018-07-03 10:54:16]: > > > From: "Gautham R. Shenoy" > > > > In the situations where snooze is the only cpuidle state due to > > firmware not exposing any platform idle states, the idle CPUs will > >

Re: [PATCH] cpuidle:powernv: Add the CPUIDLE_FLAG_POLLING for snooze

2018-07-03 Thread Vaidyanathan Srinivasan
* Gautham R Shenoy [2018-07-03 10:54:16]: > From: "Gautham R. Shenoy" > > In the situations where snooze is the only cpuidle state due to > firmware not exposing any platform idle states, the idle CPUs will > remain in snooze for a long time with interrupts disabled causing the > Hard-lockup de

[PATCH] cpuidle:powernv: Add the CPUIDLE_FLAG_POLLING for snooze

2018-07-02 Thread Gautham R. Shenoy
From: "Gautham R. Shenoy" In the situations where snooze is the only cpuidle state due to firmware not exposing any platform idle states, the idle CPUs will remain in snooze for a long time with interrupts disabled causing the Hard-lockup detector to complain. watchdog: CPU 51 detected hard LOCK