commit | 91211af0727dc30bb5927feeafa797d38cf44237 | [log] [tgz] |
---|---|---|
author | Maksim Sisov <msisov@igalia.com> | Tue Jun 28 06:28:33 2022 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 28 06:28:33 2022 |
tree | d84da5cbe47603759523c8c33b2e8c8b49001229 | |
parent | 514c52e7f9bd71858f1d73090e1c07d99f965fa6 [diff] |
Reland "Reland "exo: request release fences from viz for submitted resources"" This is a reland of commit de7ac21f5770fe41a8da8464b5c0bfc5fbbddb1f Request release fence only if explicit release cb is used and fences are available. Should fix arc tests timing out. Original change's description: > Reland "exo: request release fences from viz for submitted resources" > > This is a reland of commit a03380cfd284d08c5ff3f39ddb6d00abfe4ef4a0 > > Change: request a release fence only for zero-copy buffers > > Original change's description: > > exo: request release fences from viz for submitted resources > > > > Instead of creating release fences whenever resources are returned > > (if they are not created, which typically happens if quads are > > composited but not sent as hw overlays), ask viz to return > > resources with a release fence created. > > > > By doing this, we are not 1) including unnecessary gpu work > > 2) do not delay releasing wl_buffers. > > > > Please see more details at https://docs.google.com/document/d/1QM54jxDHWHs9NA2YOsGBdu_Rk9KSaK1BmW7Hpx5hWtE/edit?usp=sharing > > > > Bug: 1310136, 1295527, 1325329 > > Change-Id: I36ae508e738f7d8a18c8c910dafcc253647f72f3 > > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3677012 > > Commit-Queue: Maksim Sisov <msisov@igalia.com> > > Reviewed-by: Kramer Ge <fangzhoug@chromium.org> > > Cr-Commit-Position: refs/heads/main@{#1012882} > > Bug: 1310136, 1295527, 1325329, 1338335 > Change-Id: I1904fae6b4dbf5aa614ef55c34bc64bc644a008c > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3718083 > Reviewed-by: Kramer Ge <fangzhoug@chromium.org> > Commit-Queue: Maksim Sisov <msisov@igalia.com> > Cr-Commit-Position: refs/heads/main@{#1017062} Bug: 1310136, 1295527, 1325329, 1338335 Change-Id: Ib06ce0b99a29d0872f743a4ac761654d0a11ae2a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3726453 Commit-Queue: Maksim Sisov <msisov@igalia.com> Reviewed-by: Kramer Ge <fangzhoug@chromium.org> Cr-Commit-Position: refs/heads/main@{#1018561}
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.