Re: [PATCH 3/3] cpuidle,menu: smooth out measured_us calculation

On 11/3/2015 2:34 PM, r...@redhat.com wrote: Furthermore, for smaller sleep intervals, we know the chance that all the cores in the package went to the same idle state are fairly small. Dividing the measured_us by two, instead of subtracting the full exit latency when hitting a small

Re: [PATCH 3/3] cpuidle,menu: smooth out measured_us calculation

On 11/3/2015 2:34 PM, r...@redhat.com wrote: Furthermore, for smaller sleep intervals, we know the chance that all the cores in the package went to the same idle state are fairly small. Dividing the measured_us by two, instead of subtracting the full exit latency when hitting a small

[PATCH 3/3] cpuidle,menu: smooth out measured_us calculation

From: Rik van Riel The cpuidle state tables contain the maximum exit latency for each cpuidle state. On x86, that is the exit latency for when the entire package goes into that same idle state. However, a lot of the time we only go into the core idle state, not the package idle state. This

[PATCH 3/3] cpuidle,menu: smooth out measured_us calculation

From: Rik van Riel The cpuidle state tables contain the maximum exit latency for each cpuidle state. On x86, that is the exit latency for when the entire package goes into that same idle state. However, a lot of the time we only go into the core idle state, not the package idle

[PATCH 3/3] cpuidle,menu: smooth out measured_us calculation

From: Rik van Riel The cpuidle state tables contain the maximum exit latency for each cpuidle state. On x86, that is the exit latency for when the entire package goes into that same idle state. However, a lot of the time we only go into the core idle state, not the package idle state. This

[PATCH 3/3] cpuidle,menu: smooth out measured_us calculation

From: Rik van Riel The cpuidle state tables contain the maximum exit latency for each cpuidle state. On x86, that is the exit latency for when the entire package goes into that same idle state. However, a lot of the time we only go into the core idle state, not the package idle