Re: [PATCH v3 0/3] cpufreq: avoid redundant driver calls in schedutil

2016-07-21 Thread Viresh Kumar
On 13-07-16, 13:25, Steve Muckle wrote: > Invoking the cpufreq driver to set a frequency can be expensive. On platforms > with a cpufreq driver that does not support fast switching a thread must be > woken to complete the operation. IPIs will also occur if and when support to > process remote task

Re: [PATCH v3 0/3] cpufreq: avoid redundant driver calls in schedutil

2016-07-14 Thread Steve Muckle
On Thu, Jul 14, 2016 at 06:02:31PM +0800, Pingbo Wen wrote: > > Steve Muckle (3): > > cpufreq: add cpufreq_driver_resolve_freq() > > cpufreq: schedutil: map raw required frequency to driver frequency > > Tested the first two patches on db410c, only waking up irq_work 53 > times, while previous

Re: [PATCH v3 0/3] cpufreq: avoid redundant driver calls in schedutil

2016-07-14 Thread Pingbo Wen
On Thursday, July 14, 2016 04:25 AM, Steve Muckle wrote: > Invoking the cpufreq driver to set a frequency can be expensive. On platforms > with a cpufreq driver that does not support fast switching a thread must be > woken to complete the operation. IPIs will also occur if and when support to > p

[PATCH v3 0/3] cpufreq: avoid redundant driver calls in schedutil

2016-07-13 Thread Steve Muckle
Invoking the cpufreq driver to set a frequency can be expensive. On platforms with a cpufreq driver that does not support fast switching a thread must be woken to complete the operation. IPIs will also occur if and when support to process remote task wakeups is added in schedutil. Currently schedu