tracing: Avoid trace timestamp conversion to CLOCK_BOOTTIME on Posix.
Chrome traces use CLOCK_MONOTONIC as their trace clock. If the trace only contains Chrome data, it doesn't make sense to convert its timestamps to CLOCK_BOOTTIME - in fact, this conversion could lead to cross-thread timestamp skew and misaligned system tracing events on CrOS/chromecast. This patch accomplishes this by configuring the correct clock (CLOCK_MONOTONIC in this case) as trace clock for chrome-only traces, thereby instructing trace processor not to convert timestamps. Requires aosp/1315608. Bug: 1085002,1060400 Change-Id: I5ff8660a6e27f28d27f68d72bb7cf312494431bc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2210427Reviewed-by:Sami Kyöstilä <skyostil@chromium.org> Commit-Queue: Eric Seckler <eseckler@chromium.org> Cr-Commit-Position: refs/heads/master@{#771003}
Showing
Please register or sign in to comment