From: Keith Packard <keithp@keithp.com>
To: intel-gfx@lists.freedesktop.org, torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Keith Packard <keithp@keithp.com>,
Daniel Vetter <daniel@ffwll.ch>
Subject: [PATCH] Revert "drm/i915: fix infinite recursion on unbind due to ilk vt-d w/a"
Date: Fri, 16 Dec 2011 15:33:34 -0800 [thread overview]
Message-ID: <1324078414-10945-1-git-send-email-keithp@keithp.com> (raw)
This reverts commit eb1711bb94991e93669c5a1b5f84f11be2d51ea1.
This patch has been reported by two people to cause memory corruption
and application crashes. It exists solely to fix a problem with the
VT-d workarounds for Ironlake. I would back those out as well as
without this change, that work-around causes an infinite recursion for
anyone foolish enough to actually try VT-d for graphics.
So, without this patch, and when using VT-d for graphics on Ironlake,
people will experience infinite recursion crashes. With this patch, we
get memory corruption on all systems.
Cc: dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel@ffwll.ch>
Reported-by: Alex Villacís Lasso <a_villacis@palosanto.com>
Reported-by: Dirk Hohndel <dirk@hohndel.org>
Signed-off-by: Keith Packard <keithp@keithp.com>
---
drivers/gpu/drm/i915/i915_gem.c | 7 +------
1 files changed, 1 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index 60ff1b6..8359dc7 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -2026,13 +2026,8 @@ i915_wait_request(struct intel_ring_buffer *ring,
* to handle this, the waiter on a request often wants an associated
* buffer to have made it to the inactive list, and we would need
* a separate wait queue to handle that.
- *
- * To avoid a recursion with the ilk VT-d workaround (that calls
- * gpu_idle when unbinding objects with interruptible==false) don't
- * retire requests in that case (because it might call unbind if the
- * active list holds the last reference to the object).
*/
- if (ret == 0 && dev_priv->mm.interruptible)
+ if (ret == 0)
i915_gem_retire_requests_ring(ring);
return ret;
--
1.7.7.3
reply other threads:[~2011-12-16 23:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1324078414-10945-1-git-send-email-keithp@keithp.com \
--to=keithp@keithp.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®