From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Report an earlier wedged event when suspending the engines
Date: Thu, 06 Jun 2019 17:17:15 +0300 [thread overview]
Message-ID: <87muiuajdg.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <155982190941.19464.9612763812107224043@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Chris Wilson (2019-05-31 12:32:45)
>> On i915_gem_load_power_context() we do care whether or not we succeed in
>> completing the switch back to the kernel context (via idling the
>> engines). Currently, we detect if an error occurs while we wait, but we
>> do not report one if it occurred beforehand (and the status of the
>> switch is undefined). Check the current terminally wedged status on
>> entering the wait, and report it after flushing the requests, as if it
>> had occurred during our own wait.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=110824
>> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2019-06-06 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 11:32 [PATCH] drm/i915: Report an earlier wedged event when suspending the engines Chris Wilson
2019-05-31 16:29 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-06-01 21:01 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-06 11:51 ` [PATCH] " Chris Wilson
2019-06-06 14:17 ` Mika Kuoppala [this message]
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=87muiuajdg.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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