From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC] drm/i915/hangcheck: Look at instdone for all engines
Date: Mon, 10 Jun 2019 14:16:32 +0100 [thread overview]
Message-ID: <58133074-f414-9505-b8f3-239172b3d628@linux.intel.com> (raw)
In-Reply-To: <156017191664.383.14001735029510950842@skylake-alporthouse-com>
On 10/06/2019 14:05, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2019-06-10 14:01:10)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> It seems intel_engine_get_instdone is able to get instdone for all engines
>> but intel_hangcheck.c/subunits_stuck decides to ignore it for non render.
>>
>> We can just drop the check in subunits_stuck since the checks on
>> unavailable fields will always return stuck, which when bitwise and with
>> the potential unstuck instdone is harmless.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>> ---
>> Would actually using the available data improve hang detection?
>
> No, just prolong it :)
I was thinking activity on instdone would, but correctly so, no? If
functional blocks have shown a change of status, then we try again until
they too get stuck. Some improvement in false positives, but marginal I
know given the hangcheck period.
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-06-10 13:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 13:01 [RFC] drm/i915/hangcheck: Look at instdone for all engines Tvrtko Ursulin
2019-06-10 13:05 ` Chris Wilson
2019-06-10 13:16 ` Tvrtko Ursulin [this message]
2019-06-10 13:28 ` Chris Wilson
2019-06-10 15:44 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-11 14:51 ` ✓ Fi.CI.IGT: " Patchwork
2019-07-03 14:08 ` [RFC] " Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58133074-f414-9505-b8f3-239172b3d628@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox