public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [PATCH 3/5] drm/i915: don't return a spurious -EIO from intel_ring_begin
Date: Mon, 25 Jun 2012 21:32:23 +0100	[thread overview]
Message-ID: <1340656383_69674@CP5-2952> (raw)
In-Reply-To: <1340548956-4097-4-git-send-email-daniel.vetter@ffwll.ch>

On Sun, 24 Jun 2012 16:42:34 +0200, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> We have a careful logic in i915_gem_check_wedge already to asses whether
> the gpu reset has been tried already and hence whether to return -EIO
> or -EAGAIN.
> 
> Having this early check in intel_ring_begin doesn't buy us anything,
> since we'll be calling into wait_request in the usual case already
> anyway. In the corner case of not waiting for free space using the
> last_retired_head we simply need to do the same check, too.
> 
> With these changes we'll only ever get an -EIO from intel_ring_begin
> if the gpu has truely been declared dead.

The intention here was that only operations that queued a command to a
wedged GPU would trigger the EIO. That has been superseded by the error
checking during mutex acquisition. The patch looks sane, but I'd like
it split into two, one to remove the wedged check before
intel_ring_begin (with some of the rationale about it now being
superfluous) and a separate patch to reuse check_wedge().

It looks like the patch to reuse check_wedge() should be first as it is
the common theme in the series.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2012-06-25 20:33 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-24 14:42 [PATCH 0/5] gpu reset improvements Daniel Vetter
2012-06-24 14:42 ` [PATCH 1/5] drm/i915: wrap up gt powersave enabling functions Daniel Vetter
2012-06-24 23:03   ` Eugeni Dodonov
2012-06-25  7:20     ` Daniel Vetter
2012-06-29 18:51   ` Ben Widawsky
2012-06-29 21:11     ` Daniel Vetter
2012-06-24 14:42 ` [PATCH 2/5] drm/i915: make enable/disable_gt_powersave locking consistent Daniel Vetter
2012-06-24 23:03   ` Eugeni Dodonov
2012-06-25 19:08     ` Daniel Vetter
2012-06-24 14:42 ` [PATCH 3/5] drm/i915: don't return a spurious -EIO from intel_ring_begin Daniel Vetter
2012-06-25 20:32   ` Chris Wilson [this message]
2012-06-25 20:49     ` Daniel Vetter
2012-06-25 21:06       ` Chris Wilson
2012-06-25 21:48         ` Daniel Vetter
2012-06-25 22:52           ` Chris Wilson
2012-06-25 23:05             ` Daniel Vetter
2012-06-26  9:30               ` Chris Wilson
2012-06-24 14:42 ` [PATCH 4/5] drm/i915: don't trylock in the gpu reset code Daniel Vetter
2012-06-25 20:10   ` Chris Wilson
2012-06-24 14:42 ` [PATCH 5/5] drm/i915: non-interruptible sleeps can't handle -EGAIN Daniel Vetter
2012-06-25 20:23   ` Chris Wilson
2012-06-25 20:35     ` Daniel Vetter
2012-06-25 20:24   ` [PATCH] " Daniel Vetter

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=1340656383_69674@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --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