On 19-Jun 17:19, Douglas Raillard wrote:
> Hi Patrick,
Hi!
> On 5/16/19 1:55 PM, Patrick Bellasi wrote:
> > On 08-May 18:43, douglas.raill...@arm.com wrote:
> > > From: Douglas RAILLARD
> > >
> > > Avoid assuming a CPU is busy when it has begun being idle before
> > > get_next_freq() is called.
Hi Patrick,
On 5/16/19 1:55 PM, Patrick Bellasi wrote:
On 08-May 18:43, douglas.raill...@arm.com wrote:
From: Douglas RAILLARD
Avoid assuming a CPU is busy when it has begun being idle before
get_next_freq() is called. This is achieved by making sure the CPU will
not be detected as busy by ot
On 08-May 18:43, douglas.raill...@arm.com wrote:
> From: Douglas RAILLARD
>
> Avoid assuming a CPU is busy when it has begun being idle before
> get_next_freq() is called. This is achieved by making sure the CPU will
> not be detected as busy by other CPUs whenever its utilization is
> decreasing
From: Douglas RAILLARD
Avoid assuming a CPU is busy when it has begun being idle before
get_next_freq() is called. This is achieved by making sure the CPU will
not be detected as busy by other CPUs whenever its utilization is
decreasing.
Signed-off-by: Douglas RAILLARD
---
kernel/sched/cpufreq
4 matches
Mail list logo
