Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-06-01 Thread Steve Muckle
On Sat, May 21, 2016 at 12:46:06PM -0700, Steve Muckle wrote: > Hi Peter, Ingo, Hi Peter/Ingo would appreciate any thoughts you may have on the issue below. thanks, Steve > > On Thu, May 19, 2016 at 04:04:19PM -0700, Steve Muckle wrote: > > On Thu, May 19, 2016 at 11:06:14PM +0200, Rafael J. Wy

Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-05-21 Thread Steve Muckle
Hi Peter, Ingo, On Thu, May 19, 2016 at 04:04:19PM -0700, Steve Muckle wrote: > On Thu, May 19, 2016 at 11:06:14PM +0200, Rafael J. Wysocki wrote: > > > In the case of a remote update the hook has to run (or not) after it is > > > known whether preemption will occur so we don't do needless work or

Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-05-19 Thread Steve Muckle
On Thu, May 19, 2016 at 11:06:14PM +0200, Rafael J. Wysocki wrote: > > In the case of a remote update the hook has to run (or not) after it is > > known whether preemption will occur so we don't do needless work or > > IPIs. If the policy CPUs aren't known in the scheduler then the early > > hook w

Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-05-19 Thread Rafael J. Wysocki
On Thu, May 19, 2016 at 9:19 PM, Steve Muckle wrote: > On Thu, May 19, 2016 at 02:00:54PM +0200, Rafael J. Wysocki wrote: >> On Thu, May 19, 2016 at 1:33 AM, Rafael J. Wysocki wrote: >> > On Mon, May 9, 2016 at 11:20 PM, Steve Muckle >> > wrote: >> >> Without calling the cpufreq hook for a remo

Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-05-19 Thread Steve Muckle
On Thu, May 19, 2016 at 02:00:54PM +0200, Rafael J. Wysocki wrote: > On Thu, May 19, 2016 at 1:33 AM, Rafael J. Wysocki wrote: > > On Mon, May 9, 2016 at 11:20 PM, Steve Muckle > > wrote: > >> Without calling the cpufreq hook for a remote wakeup it is possible > >> for such a wakeup to go unnoti

Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-05-19 Thread Rafael J. Wysocki
On Thu, May 19, 2016 at 1:33 AM, Rafael J. Wysocki wrote: > On Mon, May 9, 2016 at 11:20 PM, Steve Muckle wrote: >> Without calling the cpufreq hook for a remote wakeup it is possible >> for such a wakeup to go unnoticed by cpufreq on the target CPU for up >> to a full tick. This can occur if the

Re: [PATCH 3/5] sched: cpufreq: call cpufreq hook from remote CPUs

2016-05-18 Thread Rafael J. Wysocki
On Mon, May 9, 2016 at 11:20 PM, Steve Muckle wrote: > Without calling the cpufreq hook for a remote wakeup it is possible > for such a wakeup to go unnoticed by cpufreq on the target CPU for up > to a full tick. This can occur if the target CPU is running a > CPU-bound task and preemption does no