From: Eric Anholt <eric@anholt.net>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 3/3] drm/i915: Attempt to uncouple object after catastrophic failure in unbind
Date: Sun, 01 Aug 2010 19:57:03 -0700 [thread overview]
Message-ID: <878w4pvi0w.fsf@pollan.anholt.net> (raw)
In-Reply-To: <1279923531-13088-4-git-send-email-chris@chris-wilson.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 558 bytes --]
On Fri, 23 Jul 2010 23:18:51 +0100, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> If we fail to flush outstanding GPU writes but return the memory to the
> system, we risk corrupting memory should the GPU recovery and complete
> those writes. On the other hand, if we bail early and free the object
> then we have a definite use-after-free and real memory corruption.
> Choose the lesser of two evils, since in order to recover from the hung
> GPU we need to completely reset it, those pending writes should
> never happen.
Applied this series to -next.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2010-08-02 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 22:18 Yet another iteration of the repeat unbind after interruption Chris Wilson
2010-07-23 22:18 ` [PATCH 1/3] drm/i915: Refactor i915_gem_retire_requests() Chris Wilson
2010-07-23 22:18 ` [PATCH 2/3] drm/i915: Repeat unbinding during free if interrupted (v6) Chris Wilson
2010-07-23 22:18 ` [PATCH 3/3] drm/i915: Attempt to uncouple object after catastrophic failure in unbind Chris Wilson
2010-08-02 2:57 ` Eric Anholt [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=878w4pvi0w.fsf@pollan.anholt.net \
--to=eric@anholt.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.