Follow up on HZ=1000 for Chrome OS kernel v4.4 |
||||||||
Issue descriptionOn previous kernel versions, we've kept the x86 config defaulting to HZ=1000, while ARM and ARM64 have been stuck on HZ=100, with several platform configs bumping this up to HZ=250 or HZ=1000. For kernel 4.4, we are going to switch everything to HZ=1000, as we couldn't identify a reason for keeping the low-HZ, and higher HZ can help with interactivity, for instance. This bug is opened to track any efforts to measure any power concerns related to this change.
,
Apr 18 2016
If Derek isn't the right person, please re-assign. Presuming that this work may make sense as part of Gru...
,
May 27 2016
,
Feb 17 2017
,
Mar 18 2017
Activating. Please assign to the right owner and the appropriate priority.
,
Apr 13 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 13 2018
Anyone care?
,
Apr 13 2018
+ some more "anybodies"
,
Apr 13 2018
We shipped all devices on 4.4 with HZ and power numbers were deemed acceptable. I do not think there is anything to do on this bug.
,
Apr 13 2018
I meant "HZ=1000" in the comment above. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by diand...@chromium.org
, Apr 18 2016Owner: dbasehore@chromium.org