Linux 5.3-rc8

Linux 5.3-rc7

Linux 5.3-rc6

Linux 5.3-rc5

Linux 5.3-rc4

sched/core: uclamp: always use enum uclamp_id for clamp_id values

The supported clamp indexes are defined in enum clamp_id however, because
of the code logic in some of the first utilization clamping series version,
sometimes we needed to use unsigned int to represent indexes.

This is not more required since the final version of the uclamp_* APIs can
always use the proper enum uclamp_id type.

Fix it with a bulk rename now that we have all the bits merged.

Signed-off-by: Patrick Bellasi <[email protected]>
Acked-by: Tejun Heo <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: Peter Zijlstra <[email protected]>

sched_tp: rename some events to match what Lisa expects

s/sched_pelt_cfs/sched_load_cfs_rq/
s/sched_pelt_se/sched_load_se/

Signed-off-by: Qais Yousef <[email protected]>

sched/events: Introduce compute_energy trace event

Introduce a new trace event reporting the result of the EAS energy
calculation done in the wake-up path, hence exposing the data used to
decide where a task should run.

This should be used for debugging only.

Signed-off-by: Quentin Perret <[email protected]>

EXPERIMENTAL: Fast UtilEst RampUp

sched/cpufreq: Align trace event behavior of fast switching

Fast switching path only emits an event for the CPU of interest, whereas the
regular path emits an event for all the CPUs that had their frequency changed,
i.e. all the CPUs sharing the same policy.

With the current behavior, looking at cpu_frequency event for a given CPU that
is using the fast switching path will not give the correct frequency signal.

Signed-off-by: Douglas RAILLARD <[email protected]>