Attachment 112919 Details for Bug 88786 – possible fix

[patch] possible fix

0001-drm-radeon-don-t-init-gpuvm-if-accel-is-disabled.patch (text/plain), 1.34 KB, created by Alex Deucher on 2015-01-28 19:40:26 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2015-01-28 19:40:26 UTC

Size: 1.34 KB

patch

obsolete

>From 651b2d3d380a7b081a97570e3da21134aedde0f9 Mon Sep 17 00:00:00 2001
>From: Alex Deucher <alexander.deucher@amd.com>
>Date: Wed, 28 Jan 2015 14:36:26 -0500
>Subject: [PATCH] drm/radeon: don't init gpuvm if accel is disabled
>
>If acceleration is disabled, it does not make sense
>to init gpuvm since nothing will use it.  Moreover,
>if radeon_vm_init() gets called it uses accel to try
>and clear the pde tables, etc. which results in a bug.
>
>Bug:
>https://bugs.freedesktop.org/show_bug.cgi?id=88786
>
>Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>Cc: stable@vger.kernel.org
>---
> drivers/gpu/drm/radeon/radeon_kms.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
>diff --git a/drivers/gpu/drm/radeon/radeon_kms.c b/drivers/gpu/drm/radeon/radeon_kms.c
>index 3cf9c1f..60751c1 100644
>--- a/drivers/gpu/drm/radeon/radeon_kms.c
>+++ b/drivers/gpu/drm/radeon/radeon_kms.c
>@@ -605,14 +605,14 @@ int radeon_driver_open_kms(struct drm_device *dev, struct drm_file *file_priv)
> 			return -ENOMEM;
> 		}
> 
>-		vm = &fpriv->vm;
>-		r = radeon_vm_init(rdev, vm);
>-		if (r) {
>-			kfree(fpriv);
>-			return r;
>-		}
>-
> 		if (rdev->accel_working) {
>+			vm = &fpriv->vm;
>+			r = radeon_vm_init(rdev, vm);
>+			if (r) {
>+				kfree(fpriv);
>+				return r;
>+			}
>+
> 			r = radeon_bo_reserve(rdev->ring_tmp_bo.bo, false);
> 			if (r) {
> 				radeon_vm_fini(rdev, vm);
>-- 
>1.8.3.1
>

Actions: View | Splinter Review

Attachments on bug 88786: 112799 | 112800 | 112801 | 112802 | 112805 | 112895 | 112898 | 112919 | 112924 | 112951 | 112957 | 112975 | 112997

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.