[tracing] Add latency ids to one of Graphics.Pipeline slices This CL adds a new latency_ids field to ChromeGraphicsPipeline and records the latency ids for the corresponding frame for the Graphics.Pipeline with STEP_GENERATE_COMPOSITOR_FRAME. This should make it easier to match input to frame production and presentation. PERFETTO_TESTS=`autoninja -C out/Default perfetto_diff_tests && out/Default/bin/run_perfetto_diff_tests` Bug: b:356429321, b:368050735 Change-Id: I2c595e7b76a5bb3523e5e1ae925828e0a8205b18 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5892083 Reviewed-by: Tushar Agarwal <agarwaltushar@google.com> Reviewed-by: Jonathan Ross <jonross@chromium.org> Reviewed-by: Mikhail Khokhlov <khokhlov@google.com> Commit-Queue: Oksana Zhuravlova <oksamyt@chromium.org> Cr-Commit-Position: refs/heads/main@{#1361819}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.