nvc0: don't put text segment into bufctx
authorIlia Mirkin <imirkin@alum.mit.edu>
Mon, 21 Jan 2019 19:24:57 +0000 (14:24 -0500)
committerIlia Mirkin <imirkin@alum.mit.edu>
Mon, 28 Jan 2019 02:47:09 +0000 (21:47 -0500)
commitd1d2bb8c07d1e20d654f558ea4750aeb09d34ff9
treee63d14c4abfe3ac47b9aa630216965c697d888db
parent0907ae35ad0e7733535516fada04948ea7125291
nvc0: don't put text segment into bufctx

The text segment is shared among multiple contexts, while each one has
its own bufctx. So when reallocating the text segment, some contexts may
end up with stale values in their bufctx's. Instead limit the exposure
to the bufctx to within a single draw.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
src/gallium/drivers/nouveau/nvc0/nvc0_compute.c
src/gallium/drivers/nouveau/nvc0/nvc0_context.c
src/gallium/drivers/nouveau/nvc0/nvc0_program.c
src/gallium/drivers/nouveau/nvc0/nvc0_surface.c
src/gallium/drivers/nouveau/nvc0/nvc0_vbo.c
src/gallium/drivers/nouveau/nvc0/nve4_compute.c