| commit | 43f30b709c28b3d6fab03bb42fa6dc8e0c3c4a77 | [log] [tgz] |
|---|---|---|
| author | Colin Blundell <blundell@chromium.org> | Mon Nov 03 08:47:13 2025 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Nov 03 08:52:11 2025 |
| tree | ce1e0d2269b71d330d6d6f0b1658a2c5fb83180f | |
| parent | 857252e5c5d6a26ef48faea974f51ed3842ad3ca [diff] |
[//gpu] Test only valid BufferUsages in MappableBuffer tests As a step toward eliminating these tests needing to call IsNativeGpuMemoryBufferConfigurationSupported() (which we're folding into its one service-side production callsite), restrict the BufferUsages that they test to the ones that are valid by platform [1]. Note: For Ozone in particular this is not statically determined; instead, we pass the possible set of valid usages (cf. [2]) and will migrate the tests to call ui::OzonePlatform::GetInstance()::IsNativePixmapConfigSupported() directly once the IsNativeGpuMemoryBufferConfigurationSupported() call is no longer needed on any other platform. [1] https://source.chromium.org/chromium/chromium/src/+/main:gpu/ipc/common/gpu_memory_buffer_support.cc;l=47?q=gpu_memory_buffer_support.cc&ss=chromium [2] https://source.chromium.org/chromium/chromium/src/+/main:ui/gfx/linux/client_native_pixmap_dmabuf.cc;drc=0926ae80f57507601481edfae11dca473ef8a900;l=101 Bug: 404905709 Change-Id: I64763446ec012ddfd289d9b3f576f862becc30f7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7105939 Reviewed-by: Vasiliy Telezhnikov <vasilyt@chromium.org> Reviewed-by: Antonio Sartori <antoniosartori@chromium.org> Commit-Queue: Colin Blundell <blundell@chromium.org> Cr-Commit-Position: refs/heads/main@{#1539211} NOKEYCHECK=True GitOrigin-RevId: ac52b7d5358a4bfc5cec8e15110af05f99703904