forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Revert "gpu: Avoid texture uploads for hardware-accelerated image dec…
…odes." This reverts commit 9dc2f05. Reason for revert: Causing linux 32-bit debug to fail all cc_unittests and viz_unittests: https://ci.chromium.org/p/chromium/builders/ci/Linux%20Tests%20%28dbg%29%281%29%2832%29/58651 Original change's description: > gpu: Avoid texture uploads for hardware-accelerated image decodes. > > This CL adds support for avoiding texture uploads for hardware > accelerated image decodes. Specifically: > > - The gpu::ImageDecodeAcceleratorWorker interface is modified so that > implementations can return the decoded image in the form of a > GpuMemoryBufferHandle. In Chrome OS, this would refer to a dmabuf. For > now, we only support YUV 4:2:0 results. > > - The gpu::ImageDecodeAcceleratorStub is modified so that it decomposes > the GpuMemoryBufferHandle coming from the hardware decoder into separate > gl::GLImages (one per plane). Each image is attached to a texture and a > SkImage is created out of each texture. These 3 SkImages are used to > create the service-side transfer cache entry which builds a single YUV > SkImage. This allows us to specify the matrix used for converting from > YUV to RGB (assumed to be the JPEG conversion matrix for now). In an > earlier prototype, I had tried to create a single GLImage and attach it > to a single texture, but the YUV-to-RGB conversion was giving wrong > results, so I decided to go the Skia route. > > - The cc::ServiceImageTransferCacheEntry is modified so that it doesn't > do texture uploads for hardware decodes. Instead, it just takes the > 3 SkImages built in the previous step plus enough data to build the > final YUV SkImage. > > Bug: 868400 > Test: the ImageDecodeAcceleratorStub unittests pass. > Change-Id: I6f435707c6b2d4368613b55399b4d6d185a84c70 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1590530 > Commit-Queue: Andres Calderon Jaramillo <andrescj@chromium.org> > Reviewed-by: Antoine Labour <piman@chromium.org> > Reviewed-by: Sunny Sachanandani <sunnyps@chromium.org> > Reviewed-by: Khushal <khushalsagar@chromium.org> > Cr-Commit-Position: refs/heads/master@{#660130} TBR=sunnyps@chromium.org,khushalsagar@chromium.org,piman@chromium.org,andrescj@chromium.org Change-Id: I60b7a80d6f0ba462afd3771f9b6d6abcd686edb2 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: 868400 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1614777 Reviewed-by: Brandon Tolsch <btolsch@chromium.org> Commit-Queue: Brandon Tolsch <btolsch@chromium.org> Cr-Commit-Position: refs/heads/master@{#660244}
- Loading branch information
Showing
18 changed files
with
140 additions
and
448 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.