Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

2017-08-07 Thread Gautham R Shenoy
>> > > >> > Subject: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for > >> > stop4 cpuidle > >> > >> I know it's not a big deal, but can we agree on the subject format? > >> > >> powerpc/powernv: Save/Restore addi

Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

2017-08-07 Thread Michael Ellerman
Gautham R Shenoy <e...@linux.vnet.ibm.com> writes: > On Tue, Aug 01, 2017 at 08:56:18PM +1000, Michael Ellerman wrote: >> "Gautham R. Shenoy" <e...@linux.vnet.ibm.com> writes: >> > >> > Subject: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additiona

Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

2017-08-06 Thread Gautham R Shenoy
Hi Michael, On Tue, Aug 01, 2017 at 08:56:18PM +1000, Michael Ellerman wrote: > "Gautham R. Shenoy" <e...@linux.vnet.ibm.com> writes: > > > > Subject: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for > > stop4 cpuidle > > I

Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

2017-08-01 Thread Michael Ellerman
"Gautham R. Shenoy" <e...@linux.vnet.ibm.com> writes: > > Subject: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for > stop4 cpuidle I know it's not a big deal, but can we agree on the subject format? powerpc/powernv: Save/Restore additional SPRs for stop4 cpuidle cheers

Re: [v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

2017-07-26 Thread Nicholas Piggin
On Fri, 21 Jul 2017 16:11:37 +0530 "Gautham R. Shenoy" wrote: > From: "Gautham R. Shenoy" > > The stop4 idle state on POWER9 is a deep idle state which loses > hypervisor resources, but whose latency is low enough that it can be > exposed via

[v3 PATCH 1/2] powernv/powerpc:Save/Restore additional SPRs for stop4 cpuidle

2017-07-21 Thread Gautham R. Shenoy
From: "Gautham R. Shenoy" The stop4 idle state on POWER9 is a deep idle state which loses hypervisor resources, but whose latency is low enough that it can be exposed via cpuidle. Until now, the deep idle states which lose hypervisor resources (eg: winkle) were only