We have had a guard against OOB array access of images on IVB for a long
time, but it can actually cause hangs on any GPU generation. This can
happen due to getting an untyped SURFACE_STATE for a typed message or
vice-versa. We didn't used to hit this with the piglit test on anything
other than I
Tested-by: Mark Janes
Jason Ekstrand writes:
> We have had a guard against OOB array access of images on IVB for a long
> time, but it can actually cause hangs on any GPU generation. This can
> happen due to getting an untyped SURFACE_STATE for a typed message or
> vice-versa. We didn't used
Jason Ekstrand writes:
> We have had a guard against OOB array access of images on IVB for a long
> time, but it can actually cause hangs on any GPU generation. This can
> happen due to getting an untyped SURFACE_STATE for a typed message or
> vice-versa.
Are you sure about that? AFAIK the
"ar
Francisco Jerez writes:
> Jason Ekstrand writes:
>
>> We have had a guard against OOB array access of images on IVB for a long
>> time, but it can actually cause hangs on any GPU generation. This can
>> happen due to getting an untyped SURFACE_STATE for a typed message or
>> vice-versa.
>
> Are
