Op 28-01-2022 om 12:02 schreef Thomas Hellström (Intel):
>
> On 1/28/22 09:57, Maarten Lankhorst wrote:
>> i915_gem_vm_close may take the lock, and we currently have no better way
>> of handling this. At least for now, allow a path in which holding vm->mutex
>> is sufficient. This is the case, beca
On 1/28/22 09:57, Maarten Lankhorst wrote:
i915_gem_vm_close may take the lock, and we currently have no better way
of handling this. At least for now, allow a path in which holding vm->mutex
is sufficient. This is the case, because the object destroy path will
forcefully take vm->mutex now.
S
i915_gem_vm_close may take the lock, and we currently have no better way
of handling this. At least for now, allow a path in which holding vm->mutex
is sufficient. This is the case, because the object destroy path will
forcefully take vm->mutex now.
Signed-off-by: Maarten Lankhorst
---
drivers/g
