vc4: Restructure the simulator mode.
authorEric Anholt <eric@anholt.net>
Tue, 11 Oct 2016 23:47:58 +0000 (16:47 -0700)
committerEric Anholt <eric@anholt.net>
Fri, 21 Oct 2016 21:12:22 +0000 (14:12 -0700)
commit78087676c98aa8884ba92e75a0a5306a8f78ad43
treeccb82acf61036bcc8d72198a247baad2f0c5f9ef
parent1d7874fa7b4683cba8f8bc78c139402b989dd9df
vc4: Restructure the simulator mode.

Rather than having simulator mode changes scattered around vc4_bufmgr.c
and vc4_screen.c, make vc4_bufmgr.c just call a vc4_simulator_ioctl, which
then dispatches to a corresponding implementation.

This will give the simulator support a centralized place to do tricks like
storing most BOs directly in simulator memory rather than copying in and
out.

This leaves special casing of mmaping BOs and execution, because of the
winsys mapping.
src/gallium/drivers/vc4/vc4_bufmgr.c
src/gallium/drivers/vc4/vc4_context.h
src/gallium/drivers/vc4/vc4_program.c
src/gallium/drivers/vc4/vc4_screen.c
src/gallium/drivers/vc4/vc4_simulator.c