bc69f9633e
Add flow trace events for command buffer flushes including all stages like ordering barrier, gpu channel flush and command buffer stub. We use (channel_id << 32 | flush_message_id) as the unique global identifier for these flows (within a special event scope). One small change is that we don't increment the flush id for every `OrderingBarrier` call if it doesn't switch contexts. This shouldn't matter in practice, but it means we won't have gaps in the flush ids anymore. Bug: 394772735 Change-Id: Ic66c5a3c57e1e95fafd4539d94effb5b95745583 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6240514 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Auto-Submit: Sunny Sachanandani <sunnyps@chromium.org> Reviewed-by: Nasko Oskov <nasko@chromium.org> Commit-Queue: Nasko Oskov <nasko@chromium.org> Commit-Queue: Sunny Sachanandani <sunnyps@chromium.org> Cr-Commit-Position: refs/heads/main@{#1417087}
Chromium
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.