igt likes to inject GPU hangs into its command streams. However, as we expect these hangs, we don't actually want them recorded in the dmesg output or stored in the i915_error_state (usually). To accommodate this allow userspace to set a flag on the context that any hang emanating from that context will not be recorded. We still do the error capture (otherwise how do we find the guilty context and know its intent?) as part of the reason for random GPU hang injection is to exercise the race conditions between the error capture and normal execution. v2: Split out the request->ringbuf error capture changes. v3: Move the flag defines next to the intel_context->flags definition
Showing the changes to include/uapi (1 of 4 files). Show all
Unified · Split
| @@ -1173,6 +1173,7 @@ struct drm_i915_gem_context_param { · 1172 unmodified lines | |||
| 1173 | #define I915_CONTEXT_PARAM_BAN_PERIOD 0x1 | 1173 | #define I915_CONTEXT_PARAM_BAN_PERIOD 0x1 |
| 1174 | #define I915_CONTEXT_PARAM_NO_ZEROMAP 0x2 | 1174 | #define I915_CONTEXT_PARAM_NO_ZEROMAP 0x2 |
| 1175 | #define I915_CONTEXT_PARAM_GTT_SIZE 0x3 | 1175 | #define I915_CONTEXT_PARAM_GTT_SIZE 0x3 |
| 1176 | #define I915_CONTEXT_PARAM_NO_ERROR_CAPTURE 0x4 | ||
| 1176 | __u64 value; | 1177 | __u64 value; |
| 1177 | }; | 1178 | }; |
| 1178 | 1179 | ||