frontends/va: Flush after unmapping VAImageBufferType
authorDavid Rosca <nowrep@gmail.com>
Thu, 7 Sep 2023 19:11:47 +0000 (21:11 +0200)
committerMarge Bot <emma+marge@anholt.net>
Fri, 8 Sep 2023 16:07:34 +0000 (16:07 +0000)
commitd6299ec258d4e991855f8c7bd0ee71f3c286234a
tree259644e6d8650a3f61103dc2b45f2ad6fd1679f5
parent136a6982515f527a82bfbdeb19c6f5c9d7ce3cf2
frontends/va: Flush after unmapping VAImageBufferType

If application changed image data we need to flush on unmap to make the
changes visible. This will also flush if the mapping was used only for
reading, but we can't know that as vaMapBuffer doesn't have a parameter
to specify if read or write is requested.

Cc: mesa-stable
Closes: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9774

Reviewed-by: Ruijing Dong <ruijing.dong@amd.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25102>
src/gallium/frontends/va/buffer.c