virgl: Don't try to use cached resources for legacy fences
Resources for fences should not be from the cache, since we are basing the fence status on the resource creation busy status. Signed-off-by: Alexandros Frantzis <alexandros.frantzis@collabora.com> Reviewed-by: Chia-I Wu <olvaffe@gmail.com>
This commit is contained in:
committed by
Chia-I Wu
parent
8089d3658a
commit
e0ffcdf16a
@@ -739,7 +739,10 @@ virgl_drm_fence_create_legacy(struct virgl_winsys *vws)
|
||||
return NULL;
|
||||
fence->fd = -1;
|
||||
|
||||
fence->hw_res = virgl_drm_winsys_resource_cache_create(vws, PIPE_BUFFER,
|
||||
/* Resources for fences should not be from the cache, since we are basing
|
||||
* the fence status on the resource creation busy status.
|
||||
*/
|
||||
fence->hw_res = virgl_drm_winsys_resource_create(vws, PIPE_BUFFER,
|
||||
PIPE_FORMAT_R8_UNORM, VIRGL_BIND_CUSTOM, 8, 1, 1, 0, 0, 0, 8);
|
||||
if (!fence->hw_res) {
|
||||
FREE(fence);
|
||||
|
||||
@@ -589,11 +589,14 @@ virgl_vtest_fence_create(struct virgl_winsys *vws)
|
||||
{
|
||||
struct virgl_hw_res *res;
|
||||
|
||||
res = virgl_vtest_winsys_resource_cache_create(vws,
|
||||
PIPE_BUFFER,
|
||||
PIPE_FORMAT_R8_UNORM,
|
||||
VIRGL_BIND_CUSTOM,
|
||||
8, 1, 1, 0, 0, 0, 8);
|
||||
/* Resources for fences should not be from the cache, since we are basing
|
||||
* the fence status on the resource creation busy status.
|
||||
*/
|
||||
res = virgl_vtest_winsys_resource_create(vws,
|
||||
PIPE_BUFFER,
|
||||
PIPE_FORMAT_R8_UNORM,
|
||||
VIRGL_BIND_CUSTOM,
|
||||
8, 1, 1, 0, 0, 0, 8);
|
||||
|
||||
return (struct pipe_fence_handle *)res;
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user