From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, Intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC 1/2] drm/i915: Improve record of hung engines in error state
Date: Wed, 4 Nov 2020 13:03:56 +0000 [thread overview]
Message-ID: <14022703-674c-be70-cf9f-c6448e1a2cd4@linux.intel.com> (raw)
In-Reply-To: <160449305596.15691.8814203162337051600@build.alporthouse.com>
On 04/11/2020 12:30, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2020-11-04 12:20:42)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Between events which trigger engine and GPU resets and capturing the error
>> state we lose information on which engine triggered the reset. Improve
>> this by passing in the hung engine mask down to error capture.
>>
>> Result is that the list of engines in user visible "GPU HANG: ecode
>> <gen>:<engines>:<ecode>, <process>" is now a list of hanging and not just
>> active engines. Most importantly the displayed process is now the one
>> which was actually hung.
>
> You could also suggest to only include the hanging engine in the report,
> as is intended to be the normal means of generating the report
I thought it is potentially useful to have a full picture, but can do
that as well.
>> diff --git a/drivers/gpu/drm/i915/i915_gpu_error.h b/drivers/gpu/drm/i915/i915_gpu_error.h
>> index 0220b0992808..3a7ca90a3436 100644
>> --- a/drivers/gpu/drm/i915/i915_gpu_error.h
>> +++ b/drivers/gpu/drm/i915/i915_gpu_error.h
>> @@ -59,6 +59,7 @@ struct i915_request_coredump {
>> struct intel_engine_coredump {
>> const struct intel_engine_cs *engine;
>>
>> + bool hung;
>> bool simulated;
>> u32 reset_count;
>>
>> @@ -218,8 +219,10 @@ struct drm_i915_error_state_buf {
>> __printf(2, 3)
>> void i915_error_printf(struct drm_i915_error_state_buf *e, const char *f, ...);
>>
>> -struct i915_gpu_coredump *i915_gpu_coredump(struct drm_i915_private *i915);
>> -void i915_capture_error_state(struct drm_i915_private *i915);
>> +struct i915_gpu_coredump *i915_gpu_coredump(struct intel_gt *gt,
>> + intel_engine_mask_t engine_mask);
>> +void i915_capture_error_state(struct intel_gt *gt,
>> + intel_engine_mask_t engine_mask);
>
> Don't forget the stubs.
Right, thanks.
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:[~2020-11-04 13:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 12:20 [Intel-gfx] [RFC 1/2] drm/i915: Improve record of hung engines in error state Tvrtko Ursulin
2020-11-04 12:20 ` [Intel-gfx] [RFC 2/2] drm/i915: Use user engine names in error state ecode Tvrtko Ursulin
2020-11-04 12:33 ` Chris Wilson
2020-11-04 13:06 ` Tvrtko Ursulin
2020-11-04 13:21 ` Chris Wilson
2020-11-04 12:30 ` [Intel-gfx] [RFC 1/2] drm/i915: Improve record of hung engines in error state Chris Wilson
2020-11-04 13:03 ` Tvrtko Ursulin [this message]
2020-11-04 13:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [RFC,1/2] " Patchwork
2020-11-04 15:37 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 13:47 [Intel-gfx] [RFC 1/2] " Tvrtko Ursulin
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=14022703-674c-be70-cf9f-c6448e1a2cd4@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