diff options
| author | Chris Wilson <[email protected]> | 2019-02-20 14:56:37 +0000 |
|---|---|---|
| committer | Chris Wilson <[email protected]> | 2019-02-20 16:31:08 +0000 |
| commit | c41166f9a145f1c4ce2961b338f9b57495ace4b5 (patch) | |
| tree | 137e4dc4097be291198f44c822469ae4804ae751 /tools/perf/scripts/python/bin | |
| parent | 47ed55a9bb9e284d46d6f2489e32a53b59152809 (diff) | |
drm/i915: Beware temporary wedging when determining -EIO
At a few points in our uABI, we check to see if the driver is wedged and
report -EIO back to the user in that case. However, as we perform the
check and reset asynchronously (where once before they were both
serialised by the struct_mutex), we may instead see the temporary wedging
used to cancel inflight rendering to avoid a deadlock during reset
(caused by either us timing out in our reset handler,
i915_wedge_on_timeout or with malice aforethought in intel_reset_prepare
for a stuck modeset). If we suspect this is the case, that is we see a
wedged driver *and* reset in progress, then wait until the reset is
resolved before reporting upon the wedged status.
v2: might_sleep() (Mika)
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=109580
Signed-off-by: Chris Wilson <[email protected]>
Cc: Mika Kuoppala <[email protected]>
Reviewed-by: Mika Kuoppala <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions