iris: Drop 'engine' from iris_batch.
authorKenneth Graunke <kenneth@whitecape.org>
Tue, 3 Sep 2019 14:19:32 +0000 (07:19 -0700)
committerMarge Bot <eric+marge@anholt.net>
Wed, 29 Jan 2020 19:53:22 +0000 (19:53 +0000)
commitafcb6625e3fe2fd7c31105f10d923762814f031e
tree54ba38c40c9315ad57fb4e51be6f49dc217d0c66
parent06b13dfed2a43d5f14d6886dfced9b5befcc159b
iris: Drop 'engine' from iris_batch.

For the moment, everything is I915_EXEC_RENDER, so this isn't necessary.
But even should that change, I don't think we want to handle multiple
engines in this manner.

Nowadays, we have batch->name (IRIS_BATCH_RENDER, IRIS_BATCH_COMPUTE,
possibly an IRIS_BATCH_BLIT for blorp batches someday), which describes
the functional usage of the batch.  We can simply check that and select
an engine for that class of work (assuming there ever is more than one).

Reviewed-by: Tapani Pälli <tapani.palli@intel.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3613>
src/gallium/drivers/iris/iris_batch.c
src/gallium/drivers/iris/iris_batch.h
src/gallium/drivers/iris/iris_context.c