[scheduler] Do not store page-level signals in FrameScheduler.
Make FrameScheduler ask PageScheduler for page-level metrics whenever it needs them (also known as pull-approach). We need to be careful to call PageScheduler::NotifyFrames each time when a signal changes. However, this patch eliminated a bunch of incorrect frame init when a page-level signal wasn't plumbed to a page. Some signals are still saved in FrameScheduler for tracing purposes only and renamed accordingly. R=alexclarke@chromium.org,skyostil@chromium.org Change-Id: I006713eac119b7619adf858beed3038b9914f274 Reviewed-on: https://chromium-review.googlesource.com/1069269 Commit-Queue: Alexander Timin <altimin@chromium.org> Reviewed-by:Alex Clarke <alexclarke@chromium.org> Cr-Commit-Position: refs/heads/master@{#561038}
Showing
Please register or sign in to comment