GitLab

For urgent threads, Chrome is now using uclamp util_min value(20)
to boost the performance instead of schedtune settings from external
upstart scripts.

This patch adds a new 'scheduler-boost-urgent=xxx' switch which makes
those urgent threads can have more aggressive boost values (0~100).

This might be needed for some ChromeOS platforms who can get better
performance from higher boosting value (e.g. Trogdor's power_VideoCall).

Additionally, existing Feature parameter names for uclamp changed to
have more general meanings:
  { MinUrgent, MaxNonUrgent, LatencySensitive } -->
  { BoostUrgent, LimitNonUrgent, LatencyTune }

BUG=1041117,b:159370915
TEST=check /proc/*/sched for all urgent threads
Signed-off-by: Ikjoon Jang <ikjn@chromium.org>
Change-Id: I07b19ed748ffba9d9a45c76310635dc359e557af
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2477712Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Reviewed-by: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#837001}