aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin/export-to-postgresql-report
diff options
context:
space:
mode:
authorChris Wilson <[email protected]>2016-07-04 08:08:39 +0100
committerChris Wilson <[email protected]>2016-07-04 08:18:24 +0100
commitbc3d674462e5df5f2b33adbfcaad9edff8b827f4 (patch)
tree460d103dfe6aff22a478b05644e84d44814ae21d /tools/perf/scripts/python/bin/export-to-postgresql-report
parentba6e0418064de8c4dee914a5eb8574affe19e6f5 (diff)
drm/i915: Allow userspace to request no-error-capture upon GPU hangs
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 Signed-off-by: Chris Wilson <[email protected]> Acked-by: Daniel Vetter <[email protected]> Reviewed-by: Dave Gordon <[email protected]> Link: http://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions