diff options
author | Ilia Mirkin <[email protected]> | 2020-05-30 02:47:42 -0400 |
---|---|---|
committer | Marge Bot <[email protected]> | 2020-05-30 17:59:24 +0000 |
commit | 6e1c47b98df384b46ff41ffbf9689a93c78c040d (patch) | |
tree | bb8a635f629d6a71bc2d746c2be17cdedde555a5 | |
parent | c48f42e178a1cc484870367c0cfe5fbbf71d86cc (diff) |
nouveau: allow invalidating coherent/persistent buffer backings
This is needed to support the core's usage of coherent buffers for
glVertex-style input. The reason why this was disallowed is that any
mappings will be invalidated. Let the state tracker worry about that,
and just reallocate when we're told.
Signed-off-by: Ilia Mirkin <[email protected]>
Reviewed-by: Karol Herbst <[email protected]>
Cc: [email protected]
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5276>
-rw-r--r-- | src/gallium/drivers/nouveau/nouveau_buffer.c | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/src/gallium/drivers/nouveau/nouveau_buffer.c b/src/gallium/drivers/nouveau/nouveau_buffer.c index 42f68fa9bdf..abb4105099a 100644 --- a/src/gallium/drivers/nouveau/nouveau_buffer.c +++ b/src/gallium/drivers/nouveau/nouveau_buffer.c @@ -850,11 +850,6 @@ nouveau_buffer_invalidate(struct pipe_context *pipe, if (unlikely(buf->base.bind & PIPE_BIND_SHARED)) return; - /* We can't touch persistent/coherent buffers */ - if (buf->base.flags & (PIPE_RESOURCE_FLAG_MAP_PERSISTENT | - PIPE_RESOURCE_FLAG_MAP_COHERENT)) - return; - /* If the buffer is sub-allocated and not currently being written, just * wipe the valid buffer range. Otherwise we have to create fresh * storage. (We don't keep track of fences for non-sub-allocated BO's.) |