diff options
| author | Pavankumar Kondeti <pkondeti@codeaurora.org> | 2016-08-12 16:12:53 +0530 |
|---|---|---|
| committer | Syed Rameez Mustafa <rameezmustafa@codeaurora.org> | 2016-08-22 14:06:36 -0700 |
| commit | 2552980f79e476b99d9f489c265a836dd61a2102 (patch) | |
| tree | 0626e0e1b6d8220ca1e14fabcf5dedecb6375459 /scripts/gcc-wrapper.py | |
| parent | 5ddfbfec063cd077dd55df47f8acf5df95a87477 (diff) | |
sched: handle frequency alert notifications better
The load reporting during frequency alert notifications is broken under
load aggregation. When aggregation is enabled, the total group busy
time is accounted towards the maximum busy CPU of a frequency domain.
If this CPU has a notification pending, it's group busy time alone is
accounted and other CPU's group busy time is completely ignored.
Similarly if any CPU other than maximum busy CPU has a pending
notification, its group busy time is accounted twice.
Maintain the frequency alert notification flag per frequency domain.
When the notification is pending, don't clip the load to 100% @ fur
for any of the CPUs in the frequency domain.
Change-Id: Iebc7d74d6fafa20430fa1c7d80f34a6ab198832d
Signed-off-by: Pavankumar Kondeti <pkondeti@codeaurora.org>
Diffstat (limited to 'scripts/gcc-wrapper.py')
0 files changed, 0 insertions, 0 deletions