panfrost: Don't set job_barrier on vertex jobs
This was a hack needed for the old transform feedback code. This barrier is handled by the explicit XFB emulation that we're using on Midgard now, so we don't need the barrier in the general case. Signed-off-by: Alyssa Rosenzweig <alyssa@collabora.com> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19760>
This commit is contained in:
parent
51457b19ce
commit
cf6b2699ca
1 changed files with 1 additions and 5 deletions
|
|
@ -2658,12 +2658,8 @@ panfrost_emit_vertex_tiler_jobs(struct panfrost_batch *batch,
|
|||
{
|
||||
struct panfrost_context *ctx = batch->ctx;
|
||||
|
||||
/* XXX - set job_barrier in case buffers get ping-ponged and we need to
|
||||
* enforce ordering, this has a perf hit! See
|
||||
* KHR-GLES31.core.vertex_attrib_binding.advanced-iterations
|
||||
*/
|
||||
unsigned vertex = panfrost_add_job(&batch->pool.base, &batch->scoreboard,
|
||||
MALI_JOB_TYPE_VERTEX, true, false,
|
||||
MALI_JOB_TYPE_VERTEX, false, false,
|
||||
ctx->indirect_draw ?
|
||||
batch->indirect_draw_job_id : 0,
|
||||
0, vertex_job, false);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue