Aperture space rollback snafu
Submitted by Chris Wilson
Assigned to Intel 3D Bugs Mailing List
Since we may update context state as we compute the batch, that state is preserved as we rollback the batch for a failed aperture check -- the subsequent emission then skips the atoms as the context state is believed to match requirements.
Affects: genX(blorp_exec) brw_dispatch_compute_common brw_draw_single_prim
The aperture rollback has been in place since
i965: Use the batch save/reset code to avoid needing the BO validate step.
The issue with believing global state for urb in particular seems to be from
i965: Stop looking at NewDriverState when emitting 3DSTATE_URB
I'm not sure if that's the only instance.