On 2017.11.16 08:11 Thomas Ilsche wrote:
> On 2017-11-09 08:38, Len Brown wrote:
>> From: Len Brown
>>
>> While there are several mechanisms (cmdline, sysfs, PM_QOS) to limit
>> cpuidle to shallow idle states, there is no simple mechanism
>> to give the hardware permission to enter the deeptest s
On 2017-11-09 08:38, Len Brown wrote:
From: Len Brown
While there are several mechanisms (cmdline, sysfs, PM_QOS) to limit
cpuidle to shallow idle states, there is no simple mechanism
to give the hardware permission to enter the deeptest state permitted by PM_QOS.
Here we create the "cpuidle.u
Hi Len,
Other feedback notwithstanding, works fine for me.
Just a small typo type comment:
On 2017.11.08 23:39 Len Brown wrote:
...[snip]...
> Here we create the "cpuidle.use_deepest" modparam to provide this capability.
>
> "cpuidle.use_deepest=Y" can be set at boot-time, and
> /sys/module/cp
On 2017-11-09 at 02:38:51 -0500, Len Brown wrote:
> From: Len Brown
>
[cut]
> +/**
> + * cpuidle_find_deepest_state_qos - Find the deepest available idle state.
> + * @drv: cpuidle driver for the given CPU.
> + * @dev: cpuidle device for the given CPU.
> + * Honors PM_QOS
> + */
> +int cpuidle_
Hi Len
On 9 November 2017 at 08:38, Len Brown wrote:
> From: Len Brown
>
> While there are several mechanisms (cmdline, sysfs, PM_QOS) to limit
> cpuidle to shallow idle states, there is no simple mechanism
> to give the hardware permission to enter the deeptest state permitted by
> PM_QOS.
an
From: Len Brown
While there are several mechanisms (cmdline, sysfs, PM_QOS) to limit
cpuidle to shallow idle states, there is no simple mechanism
to give the hardware permission to enter the deeptest state permitted by PM_QOS.
Here we create the "cpuidle.use_deepest" modparam to provide this cap
6 matches
Mail list logo
