diff options
| author |   John Harrison <John.C.Harrison@Intel.com> | 2022-07-27 19:42:25 -0700 |
|---|---|---|
| committer | John Harrison <John.C.Harrison@Intel.com> | 2022-07-29 10:35:59 -0700 |
| commit | dd9d3cbe9efcdb2a0d88c80d0e492ccae54a5b63 (patch) | |
| tree | 3d9dd7ac10389a275411f5315393201593bd41a7 /tools/testing/selftests/exec/git:/ssh:/git@git.zx2c4.com | |
| parent | drm/i915/guc: Support larger contexts on newer hardware (diff) | |
| download | linux-dev-dd9d3cbe9efcdb2a0d88c80d0e492ccae54a5b63.tar.xz linux-dev-dd9d3cbe9efcdb2a0d88c80d0e492ccae54a5b63.zip | |
drm/i915/guc: Don't abort on CTB_UNUSED status
When the KMD sends a CLIENT_RESET request to GuC (as part of the
suspend sequence), GuC will mark the CTB buffer as 'UNUSED'. If the
KMD then checked the CTB queue, it would see a non-zero status value
and report the buffer as corrupted.
Technically, no G2H messages should be received once the CLIENT_RESET
has been sent. However, if a context was outstanding on an engine then
it would get reset and a reset notification would be sent. So, don't
actually treat UNUSED as a catastrophic error. Just flag it up as
unexpected and keep going.
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220728024225.2363663-7-John.C.Harrison@Intel.com
Diffstat (limited to 'tools/testing/selftests/exec/git:/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions