[PATCH] drm/radeon: fix adding all VAs to the freed list on remove v2

2015-06-30 Thread Michel Dänzer
On 26.06.2015 19:31, Christian König wrote: > From: Christian König > > We only should do so when the BO_VA was actually mapped. > Otherwise we get a nice error message on the next CS. > > v2: It actually doesn't matter if it was invalidated or not, > if it was mapped we need to clear the

[PATCH] drm/radeon: fix adding all VAs to the freed list on remove

2015-06-26 Thread Michel Dänzer
On 26.06.2015 17:41, Christian König wrote: > From: Christian König > > We only should do so when the BO_VA was actually mapped. > Otherwise we get a nice error message on the next CS. > > Signed-off-by: Christian König Tested-by: Michel Dänzer -- Earthling Michel Dänzer

[PATCH] drm/radeon: fix adding all VAs to the freed list on remove v2

2015-06-26 Thread Alex Deucher
On Fri, Jun 26, 2015 at 6:31 AM, Christian König wrote: > From: Christian König > > We only should do so when the BO_VA was actually mapped. > Otherwise we get a nice error message on the next CS. > > v2: It actually doesn't matter if it was invalidated or not, > if it was mapped we need to

[PATCH] drm/radeon: fix adding all VAs to the freed list on remove v2

2015-06-26 Thread Christian König
From: Christian König We only should do so when the BO_VA was actually mapped. Otherwise we get a nice error message on the next CS. v2: It actually doesn't matter if it was invalidated or not, if it was mapped we need to clear the area where it was mapped. Signed-off-by: Christian König

[PATCH] drm/radeon: fix adding all VAs to the freed list on remove

2015-06-26 Thread Christian König
From: Christian König We only should do so when the BO_VA was actually mapped. Otherwise we get a nice error message on the next CS. Signed-off-by: Christian König --- drivers/gpu/drm/radeon/radeon_vm.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/rad