Attachment 70112 Details for Bug 57122 – disable unbound tracking

[patch] disable unbound tracking

0001-drm-i915-disable-unbound-tracking.patch (text/plain), 1.25 KB, created by Daniel Vetter on 2012-11-15 13:15:52 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Daniel Vetter

Created: 2012-11-15 13:15:52 UTC

Size: 1.25 KB

patch

obsolete

>From ee5f1b0989c1daacb380b6011d7fd4af9c765cc7 Mon Sep 17 00:00:00 2001
>From: Daniel Vetter <daniel.vetter@ffwll.ch>
>Date: Thu, 15 Nov 2012 14:30:09 +0100
>Subject: [PATCH] drm/i915: disable unbound tracking
>
>This essentially disables the unbound list introduce in
>
>commit 6c085a728cf000ac1865d66f8c9b52935558b328
>Author: Chris Wilson <chris@chris-wilson.co.uk>
>Date:   Mon Aug 20 11:40:46 2012 +0200
>
>    drm/i915: Track unbound pages
>
>We do keep around all the related infrastructure work though
>(specifically the page_pin_count) since those are required to make
>dma_buf work somewhat more sanely (and less buggy), amongst other
>thigns.
>
>Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
>---
> drivers/gpu/drm/i915/i915_gem.c |    4 ++++
> 1 file changed, 4 insertions(+)
>
>diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
>index 107f09b..6a3c118 100644
>--- a/drivers/gpu/drm/i915/i915_gem.c
>+++ b/drivers/gpu/drm/i915/i915_gem.c
>@@ -2466,6 +2466,10 @@ i915_gem_object_unbind(struct drm_i915_gem_object *obj)
> 	obj->gtt_space = NULL;
> 	obj->gtt_offset = 0;
> 
>+	/* Drop backing storage. Only fails when the backing storage is pinned,
>+	 * hence we can ignore the return value. */
>+	i915_gem_object_put_pages(obj);
>+
> 	return 0;
> }
> 
>-- 
>1.7.10.4
>

Actions: View | Splinter Review

Attachments on bug 57122: 70081 | 70082 | 70083 | 70084 | 70112 | 70170 | 70265 | 70267 | 70269 | 70276 | 70387 | 70388 | 70389 | 70484 | 70485 | 70486 | 70578 | 70976 | 71440 | 71682 | 71702 | 71780 | 71806 | 71932 | 72905

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.