diff options
author | Valentin Schneider <[email protected]> | 2019-11-15 10:39:08 +0000 |
---|---|---|
committer | Ingo Molnar <[email protected]> | 2019-11-17 10:46:05 +0100 |
commit | 7763baace1b738d65efa46d68326c9406311c6bf (patch) | |
tree | 4fc5e78ebfb5af865bb77c32e9596ba7726a8d9e /tools/perf/scripts/python/export-to-postgresql.py | |
parent | a0e813f26ebcb25c0b5e504498fbd796cca1a4ba (diff) |
sched/uclamp: Fix overzealous type replacement
Some uclamp helpers had their return type changed from 'unsigned int' to
'enum uclamp_id' by commit
0413d7f33e60 ("sched/uclamp: Always use 'enum uclamp_id' for clamp_id values")
but it happens that some do return a value in the [0, SCHED_CAPACITY_SCALE]
range, which should really be unsigned int. The affected helpers are
uclamp_none(), uclamp_rq_max_value() and uclamp_eff_value(). Fix those up.
Note that this doesn't lead to any obj diff using a relatively recent
aarch64 compiler (8.3-2019.03). The current code of e.g. uclamp_eff_value()
properly returns an 11 bit value (bits_per(1024)) and doesn't seem to do
anything funny. I'm still marking this as fixing the above commit to be on
the safe side.
Signed-off-by: Valentin Schneider <[email protected]>
Reviewed-by: Qais Yousef <[email protected]>
Acked-by: Vincent Guittot <[email protected]>
Cc: [email protected]
Cc: Linus Torvalds <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Cc: [email protected]
Fixes: 0413d7f33e60 ("sched/uclamp: Always use 'enum uclamp_id' for clamp_id values")
Link: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions