tracing: Always tie sequence-local clocks to boottime
Previously, we were relating the microsecond-granularity sequence-local clocks to CLOCK_MONOTONIC, which meant that trace processor has to find a 2-step path via CLOCK_MONOTONIC to CLOCK_BOOTTIME, which is rather slow. Instead, tie the sequence-local monotonic clocks directly to CLOCK_BOOTTIME in their ClockSnapshots. Bug: 928738, b/148506711 Change-Id: I8247d0ca1acb76e661675cd9a732942b4d2401f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2027369 Commit-Queue: Eric Seckler <eseckler@chromium.org> Reviewed-by:Sami Kyöstilä <skyostil@chromium.org> Cr-Commit-Position: refs/heads/master@{#736370}
Showing
Please register or sign in to comment