Yes, that seems to fix the problem!
You can have my
Tested-by: Kai Wasserbäch
Thanks,
Kai
Christian König wrote on 19.11.2014 17:18:
> Ah! Yes of course, we have changed we way memory is allocated for the BO list
> in
> the meantime.
>
> Does it work if you replace the last patch in the
Ah! Yes of course, we have changed we way memory is allocated for the BO
list in the meantime.
Does it work if you replace the last patch in the list with the attached
one?
Thanks for pointing this out,
Christian.
Am 19.11.2014 um 16:43 schrieb Kai Wasserbäch:
> Dear Christian,
> Christian
Dear Christian,
Christian König wrote on 19.11.2014 14:35:
> Am 19.11.2014 um 14:16 schrieb Kai Wasserbäch:
>> Dear Christian,
>> Christian König wrote on 19.11.2014 14:01:
>>> From: Christian König
>>>
>>> This way the necessary VM update is kicked off immediately
>>> if all BOs involved are
Am 19.11.2014 um 14:16 schrieb Kai Wasserbäch:
> Dear Christian,
> Christian König wrote on 19.11.2014 14:01:
>> From: Christian König
>>
>> This way the necessary VM update is kicked off immediately
>> if all BOs involved are in GPU accessible memory.
>>
>> v2: fix vm lock
>> v3: immediately
Dear Christian,
Christian König wrote on 19.11.2014 14:01:
> From: Christian König
>
> This way the necessary VM update is kicked off immediately
> if all BOs involved are in GPU accessible memory.
>
> v2: fix vm lock
> v3: immediately update unmaps as well
>
> Signed-off-by: Christian
From: Christian König
This way the necessary VM update is kicked off immediately
if all BOs involved are in GPU accessible memory.
v2: fix vm lock
v3: immediately update unmaps as well
Signed-off-by: Christian König
---
drivers/gpu/drm/radeon/radeon_gem.c | 64