drm/i915: Do not leak VMAs (and PPGTT VMs) of imported flinked objects
Subsystems (2)
PATCH 1/1 drm/i915: Do not leak VMAs (and PPGTT VMs) of imported flinked objects
From: Tvrtko Ursulin <[email protected]>
If a client instantiates a VMA against an imported object (flink) this VMA will not get unbound when the object is closed.
This happens because the exporter holds a reference count on the object and will also keep a reference to the PPGTT VM.
In real life this happens with xorg-driver-intel and fbcon takeover. Latter is copied from via the flink name and when Xorg process exists one VMA remains dangling with a now unreachable VM.
Testcase: igt/gem_ppgtt/flink-vs-ctx-vm-leak
--- drivers/gpu/drm/i915/i915_drv.c | 1 + drivers/gpu/drm/i915/i915_drv.h | 2 ++ drivers/gpu/drm/i915/i915_gem.c | 63 ++++++++++++++++++++++++++++++++--------- 3 files changed, 53 insertions(+), 13 deletions(-)
drivers/gpu/drm/i915/i915_drv.c +1 -0
@@ -1630,6 +1630,7 @@ static struct drm_driver driver = { .debugfs_init = i915_debugfs_init, .debugfs_cleanup = i915_debugfs_cleanup, #endif + .gem_close_object = i915_gem_close_object, .gem_free_object = i915_gem_free_object, .gem_vm_ops = &i915_gem_vm_ops,
drivers/gpu/drm/i915/i915_drv.h +2 -0
@@ -2635,6 +2635,8 @@ struct drm_i915_gem_object *i915_gem_alloc_object(struct drm_device *dev, size_t size);void i915_init_vm (struct drm_i915_private *dev_priv,struct i915_address_space *vm); +void i915_gem_close_object (struct drm_gem_object *gem_obj, +struct drm_file *file);void i915_gem_free_object (struct drm_gem_object *obj);void i915_gem_vma_destroy (struct i915_vma *vma);
drivers/gpu/drm/i915/i915_gem.c +50 -13
76 lines not on this page · raw message
Signature · 6 lines
2.3.5 _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 88 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
If a client instantiates a VMA against an imported object (flink) this VMA will not get unbound when the object is closed.
This happens because the exporter holds a reference count on the object and will also keep a reference to the PPGTT VM.
In real life this happens with xorg-driver-intel and fbcon takeover. Latter is copied from via the flink name and when Xorg process exists one VMA remains dangling with a now unreachable VM.
Signed-off-by Tvrtko Ursulin <[email protected]>Cc Chris Wilson <[email protected]>Testcase: igt/gem_ppgtt/flink-vs-ctx-vm-leak
--- drivers/gpu/drm/i915/i915_drv.c | 1 + drivers/gpu/drm/i915/i915_drv.h | 2 ++ drivers/gpu/drm/i915/i915_gem.c | 63 ++++++++++++++++++++++++++++++++--------- 3 files changed, 53 insertions(+), 13 deletions(-)drivers/gpu/drm/i915/i915_drv.c +1
-0@@ -1630,6 +1630,7 @@ static struct drm_driver driver = { .debugfs_init = i915_debugfs_init, .debugfs_cleanup = i915_debugfs_cleanup, #endif + .gem_close_object = i915_gem_close_object, .gem_free_object = i915_gem_free_object, .gem_vm_ops = &i915_gem_vm_ops,drivers/gpu/drm/i915/i915_drv.h +2
-0@@ -2635,6 +2635,8 @@ struct drm_i915_gem_object *i915_gem_alloc_object(struct drm_device *dev, size_t size);void i915_init_vm (struct drm_i915_private *dev_priv,struct i915_address_space *vm); +void i915_gem_close_object (struct drm_gem_object *gem_obj, +struct drm_file *file);void i915_gem_free_object (struct drm_gem_object *obj);void i915_gem_vma_destroy (struct i915_vma *vma);drivers/gpu/drm/i915/i915_gem.c +34
-0@@ -4523,6 +4523,55 @@ static bool discard_backing_storage(struct drm_i915_gem_object *obj)return atomic_long_read (&obj->base.filp->f_count) ==1 ; } +static void i915_gem_unbind_vma (struct drm_i915_private *dev_priv, +struct i915_vma *vma) +{ +if (WARN_ON (i915_vma_unbind (vma) == -ERESTARTSYS )) { +bool was_interruptible; + + was_interruptible = dev_priv->mm.interruptible; + dev_priv->mm.interruptible = false; + +WARN_ON (i915_vma_unbind (vma)); + + dev_priv->mm.interruptible = was_interruptible; + } +} + +void i915_gem_close_object (struct drm_gem_object *gem_obj, +struct drm_file *file) +{ +struct drm_i915_gem_object *obj =to_intel_bo (gem_obj); +struct drm_device *dev = obj->base.dev; +struct drm_i915_file_private *file_priv = file->driver_priv; +struct i915_vma *vma, *next; +struct i915_hw_ppgtt *ppgtt; + +mutex_lock (&dev->struct_mutex); + +/* +* Release all VMAs associated with this client's PPGTT. +* +* This is to avoid potentially unreachable VMAs since contexts can have +* shorter lifetime than objects. Meaning if a client has a reference to +* an object (flink) and an instantiated VMA, when it exists neither VMA +* will be unbound (since object free won't run), nor the PPGTT VM +* freed (since VMA holds a reference to it).
drivers/gpu/drm/i915/i915_gem.c static bool discard_backing_storage(struct drm_i915_gem_object *obj) · line 4569
Quoted 10 lines
drivers/gpu/drm/i915/i915_gem.c +10
-0+*/ +list_for_each_entry_safe (vma, next, &obj->vma_list, vma_link) { +if (i915_is_ggtt (vma->vm)) +continue ; + + ppgtt = (struct i915_hw_ppgtt *)vma->vm; +if (ppgtt->file_priv != file_priv) +continue ; + +i915_gem_unbind_vma (dev->dev_private, vma);
No we can't do this, as it makes close sync and so can have disasterous effects on performance (though mitigated chiefly by userspace agressively caching bo) and also the unbind is very likely to fail, though admittedly the fbcon copy should be before X starts (ab)using signals - hence nasty WARN_ON.
Plus also walking this linear list is quite painful in certain abusive tests. My preference for fixing this bug would be via vma active references and auto-unbinding on retirement after a close.
Expect some fun patches in your inbox Tvrtko :-p
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 106 lines · Chris Wilson
Quoted 88 lines · Tvrtko Ursulin
From: Tvrtko Ursulin <[email protected]>
If a client instantiates a VMA against an imported object (flink) this VMA will not get unbound when the object is closed.
This happens because the exporter holds a reference count on the object and will also keep a reference to the PPGTT VM.
In real life this happens with xorg-driver-intel and fbcon takeover. Latter is copied from via the flink name and when Xorg process exists one VMA remains dangling with a now unreachable VM.
Signed-off-by Tvrtko Ursulin <[email protected]>Cc Chris Wilson <[email protected]>Testcase: igt/gem_ppgtt/flink-vs-ctx-vm-leak
--- drivers/gpu/drm/i915/i915_drv.c | 1 + drivers/gpu/drm/i915/i915_drv.h | 2 ++ drivers/gpu/drm/i915/i915_gem.c | 63 ++++++++++++++++++++++++++++++++--------- 3 files changed, 53 insertions(+), 13 deletions(-)drivers/gpu/drm/i915/i915_drv.c +1
-0@@ -1630,6 +1630,7 @@ static struct drm_driver driver = { .debugfs_init = i915_debugfs_init, .debugfs_cleanup = i915_debugfs_cleanup, #endif + .gem_close_object = i915_gem_close_object, .gem_free_object = i915_gem_free_object, .gem_vm_ops = &i915_gem_vm_ops,drivers/gpu/drm/i915/i915_drv.h +2
-0@@ -2635,6 +2635,8 @@ struct drm_i915_gem_object *i915_gem_alloc_object(struct drm_device *dev, size_t size);void i915_init_vm (struct drm_i915_private *dev_priv,struct i915_address_space *vm); +void i915_gem_close_object (struct drm_gem_object *gem_obj, +struct drm_file *file);void i915_gem_free_object (struct drm_gem_object *obj);void i915_gem_vma_destroy (struct i915_vma *vma);drivers/gpu/drm/i915/i915_gem.c +34
-0@@ -4523,6 +4523,55 @@ static bool discard_backing_storage(struct drm_i915_gem_object *obj)return atomic_long_read (&obj->base.filp->f_count) ==1 ; } +static void i915_gem_unbind_vma (struct drm_i915_private *dev_priv, +struct i915_vma *vma) +{ +if (WARN_ON (i915_vma_unbind (vma) == -ERESTARTSYS )) { +bool was_interruptible; + + was_interruptible = dev_priv->mm.interruptible; + dev_priv->mm.interruptible = false; + +WARN_ON (i915_vma_unbind (vma)); + + dev_priv->mm.interruptible = was_interruptible; + } +} + +void i915_gem_close_object (struct drm_gem_object *gem_obj, +struct drm_file *file) +{ +struct drm_i915_gem_object *obj =to_intel_bo (gem_obj); +struct drm_device *dev = obj->base.dev; +struct drm_i915_file_private *file_priv = file->driver_priv; +struct i915_vma *vma, *next; +struct i915_hw_ppgtt *ppgtt; + +mutex_lock (&dev->struct_mutex); + +/* +* Release all VMAs associated with this client's PPGTT. +* +* This is to avoid potentially unreachable VMAs since contexts can have +* shorter lifetime than objects. Meaning if a client has a reference to +* an object (flink) and an instantiated VMA, when it exists neither VMA +* will be unbound (since object free won't run), nor the PPGTT VM +* freed (since VMA holds a reference to it). drivers/gpu/drm/i915/i915_gem.c static bool discard_backing_storage(struct drm_i915_gem_object *obj) · line 4569
Quoted 10 lines
drivers/gpu/drm/i915/i915_gem.c +10
-0+*/ +list_for_each_entry_safe (vma, next, &obj->vma_list, vma_link) { +if (i915_is_ggtt (vma->vm)) +continue ; + + ppgtt = (struct i915_hw_ppgtt *)vma->vm; +if (ppgtt->file_priv != file_priv) +continue ; + +i915_gem_unbind_vma (dev->dev_private, vma);No we can't do this, as it makes close sync and so can have disasterous effects on performance (though mitigated chiefly by userspace agressively caching bo) and also the unbind is very likely to fail, though admittedly the fbcon copy should be before X starts (ab)using signals - hence nasty
WARN_ON.
Quoted 3 lines
Plus also walking this linear list is quite painful in certain abusive tests. My preference for fixing this bug would be via vma active references and auto-unbinding on retirement after a close.
Why this is any different today with GEM_CLOSE having pretty similar VMA unbind loop? Is the typical (and interesting) case not that GEM_CLOSE will trigger gem_object_close and gem_object_free at the same invocation?
Quoted 1 line
Expect some fun patches in your inbox Tvrtko :-p
Ok, just don't make them depend on everything. :)
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 6 lines · Tvrtko Ursulin
Quoted 6 lines
No we can't do this, as it makes close sync and so can have disasterous effects on performance (though mitigated chiefly by userspace agressively caching bo) and also the unbind is very likely to fail, though admittedly the fbcon copy should be before X starts (ab)using signals - hence nasty
WARN_ON.
Quoted 8 lines
Quoted 3 lines
Plus also walking this linear list is quite painful in certain abusive tests. My preference for fixing this bug would be via vma active references and auto-unbinding on retirement after a close.
Why this is any different today with
GEM_CLOSEhaving pretty similar VMA unbind loop? Is the typical (and interesting) case not thatGEM_CLOSEwill triggergem_object_closeandgem_object_freeat the same invocation?
We have such a cleanup loop in free_object, but we have an active reference to ensure that we only do so once the object is idle (and unbinding won't cause to wait).
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 11 lines · Chris Wilson
Quoted 10 lines · Tvrtko Ursulin
Quoted 9 lines
No we can't do this, as it makes close sync and so can have disasterous effects on performance (though mitigated chiefly by userspace agressively caching bo) and also the unbind is very likely to fail, though admittedly the fbcon copy should be before X starts (ab)using signals - hence nasty
WARN_ON.Plus also walking this linear list is quite painful in certain abusive tests. My preference for fixing this bug would be via vma active references and auto-unbinding on retirement after a close.
Quoted 8 lines
Quoted 4 lines
Why this is any different today with
GEM_CLOSEhaving pretty similar VMA unbind loop? Is the typical (and interesting) case not thatGEM_CLOSEwill triggergem_object_closeandgem_object_freeat the same invocation?We have such a cleanup loop in
free_object, but we have an active reference to ensure that we only do so once the object is idle (and unbinding won't cause to wait).
Is that a predominant situation - closing of active objects vs inactive? It would be surprising (to me).
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoted 18 lines · Tvrtko Ursulin
Quoted 16 lines · Chris Wilson
Quoted 14 lines · Tvrtko Ursulin
Quoted 9 lines
No we can't do this, as it makes close sync and so can have disasterous effects on performance (though mitigated chiefly by userspace agressively caching bo) and also the unbind is very likely to fail, though admittedly the fbcon copy should be before X starts (ab)using signals - hence nasty
WARN_ON.Plus also walking this linear list is quite painful in certain abusive tests. My preference for fixing this bug would be via vma active references and auto-unbinding on retirement after a close.
Why this is any different today with
GEM_CLOSEhaving pretty similar VMA unbind loop? Is the typical (and interesting) case not thatGEM_CLOSEwill triggergem_object_closeandgem_object_freeat the same invocation?
Quoted 6 lines
Quoted 3 lines
We have such a cleanup loop in
free_object, but we have an active reference to ensure that we only do so once the object is idle (and unbinding won't cause to wait).Is that a predominant situation - closing of active objects vs inactive? It would be surprising (to me).
Relatively rare due to our aggressive userspace caching. (You can look at a couple of other drivers which don't use either such an aggressive cache or employ active references to see how much it hurts *cough* nouveau *cough*). However, we do hit it often enough through flinked buffers which can't be safely reused and so get closed as soon as we finish referencing them in commands.
-Chris
Signature · 5 lines
Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Task id: 6235 -------------------------------------Summary-------------------------------------
Platform Delta drm-intel-nightly Series Applied
PNV 276/276 276/276 ILK 302/302 302/302 SNB 318/318 318/318 IVB 341/341 341/341 BYT 287/287 287/287 BDW -35 318/318 283/318
-------------------------------------Detailed-------------------------------------
Platform Test drm-intel-nightly Series Applied
*BDW igt@gem_fenced_exec_thrash@no-spare-fences-busy-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@forked-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@forked-interruptible-faulting-reloc PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrash-inactive PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@forked-interruptible-faulting-reloc-thrashing PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@forked-interruptible-thrash-inactive PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@forked-interruptible-thrashing PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_persistent_relocs@interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@faulting-reloc-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@forked-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@forked-interruptible-faulting-reloc PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@forked-interruptible-faulting-reloc-thrash-inactive PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@forked-interruptible-faulting-reloc-thrashing PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@forked-interruptible-thrash-inactive PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@forked-interruptible-thrashing PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_reloc_vs_gpu@interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_render_copy_redux@flink-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_render_copy_redux@interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-mempressure-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-multifd-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-multifd-mempressure-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-swapping-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-swapping-mempressure-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-swapping-multifd-interruptible PASS(2) DMESG_WARN(2)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-sync-swapping-multifd-mempressure-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-unsync-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-unsync-mempressure-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-unsync-multifd-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-unsync-multifd-mempressure-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-unsync-swapping-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_userptr_blits@forked-unsync-swapping-mempressure-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_write_read_ring_switch@blt2bsd-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_write_read_ring_switch@blt2render-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
*BDW igt@gem_write_read_ring_switch@blt2vebox-interruptible PASS(2) DMESG_WARN(1)
(dmesg patch applied)WARNING:at_drivers/gpu/drm/i915/i915_gem.c:#i915_gem_unbind_vma[i915]()@WARNING:.* at .* i915_gem_unbind_vma
Note: You need to pay more attention to line start with '*'
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx