commit 26a9316f4581e5b0bcaa5096c65ff9f3d57ae282
author Matthew Andrews <mattandr@microsoft.com> Tue May 27 20:21:03 2025
committer Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> Tue May 27 20:21:03 2025
tree 1707f9fca5bfb95e016426d73136d0e1d466c6ae
parent 61d1b4c9e4c0dcfcf04f759c6ee5cceacf0daabf

Disable shared image support for Intel VP9 and disable shared device for Intel

When the shared image encode and video processing features are enabled,
the encode-decode test fails with VP9 due to color corruption in the
output frames. Disable shared image support with VP9 on Intel systems
until this issue can be fixed.

Also, there is a rare issue where the Intel encoder MFT acquires the
device lock but does not release it. This causes a rare GPU process hang
when Graphite is enabled. To resolve this, have MFVEA use a separate D3D
device in this case. D3DImageBacking already uses a copy representation
when the caller device is not the shared image system device, but I
needed to update this to synchronize access since I originally added it
only for decoder textures in Ganesh.

Change-Id: I6a677cf4c65e359fcf1e3c7d6d933f31b8374a25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6541526
Reviewed-by: Erik Anderson <Erik.Anderson@microsoft.com>
Commit-Queue: Matthew Andrews <mattandr@microsoft.com>
Reviewed-by: Chunbo Hua <chunbo.hua@intel.com>
Reviewed-by: Eugene Zemtsov <eugene@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1466120}