Hi Liviu,

Regarding your comments about using the C-state instead of the residency, we based off of the existing mcpm_suspend call which currently takes residency (with a 0 meaning lowest power).

We used calls (including mcpm_suspend) in the hot plug/suspend path.  However, it does not know about c-states.  I suspect others may want to do the same.  Do you know how suspend is done on tc2?

Regarding guest kernels, I don't think I understand the implications.  If we migrate between cores (having different parameters) in the middle of a cstate transition, can we have correct behavior?  Wouldn't it be worse to migrate to a lower c-state then we had intended?

Thanks,

Sebastian


On 15 May 2013 10:07, Jon Medhurst (Tixy) <tixy@linaro.org> wrote:
On Wed, 2013-05-15 at 09:49 -0700, Sebastian Capella wrote:
> Thanks Daniel!
>
> Liviu,
>
> I have been using on the linux-linaro branch in the linux-linaro-tracking
> repository here:
>
> https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=shortlog;h=refs/heads/linux-linaro
>

Generally, that's the Linaro kernel tree people should use and what is
built daily and released monthly.

It's just it hasn't moved to 3.10 yet (will do in the next day or so)
but the topic branches which feed into it (that Liviu pointed out) have
already made that move.

--
Tixy