OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

svga: Ignore redefine_user_buffer calls

Browse Source 
We currently always treat contents of user-buffers as volatile so
we don't need to take any particular action when the state tracker
announces that the contents has changed.

Signed-off-by: Thomas Hellstrom <thellstrom@vmware.com>
This commit is contained in:
Thomas Hellstrom
2011-06-29 13:17:02 +02:00
parent 762518d26a
commit a8cf4b6acf
1 changed files with 2 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
src/gallium/drivers/svga/svga_resource_buffer_upload.c
View File

@@ -651,8 +651,6 @@ svga_redefine_user_buffer(struct pipe_context *pipe,
unsigned offset,
unsigned size)
{
struct svga_screen *ss = svga_screen(pipe->screen);
struct svga_context *svga = svga_context(pipe);
struct svga_buffer *sbuf = svga_buffer(resource);
assert(sbuf->user);
@@ -661,19 +659,8 @@ svga_redefine_user_buffer(struct pipe_context *pipe,
assert(!sbuf->hwbuf);
/*
* Release any uploaded user buffer.
*
* TODO: As an optimization, we could try to update the uploaded buffer
* instead.
* We always treat the contents of user-buffers as volatile,
* so no particular action needed here.
*/
pipe_resource_reference(&sbuf->uploaded.buffer, NULL);
pipe_mutex_lock(ss->swc_mutex);
sbuf->key.size.width = sbuf->b.b.width0 = offset + size;
pipe_mutex_unlock(ss->swc_mutex);
svga->dirty |= SVGA_NEW_VBUFFER | SVGA_NEW_VELEMENT;
}