drm: Revert general use of struct drm_gem_object.dma_buf
Subsystems (6)
Thomas Zimmermann
maintainerv2 cover drm: Revert general use of struct drm_gem_object.dma_buf
Revert the use of drm_gem_object.dma_buf back to .import_attach->dmabuf in the affected places. Separates references to imported and exported DMA bufs within a GEM object; as before.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
v2:
- extended commit messages (Sima)
- drop the GEM-handle changes to be resolved separately
Thomas Zimmermann (7):
Revert "drm/virtio: Use dma_buf from GEM object instance" Revert "drm/vmwgfx: Use dma_buf from GEM object instance" Revert "drm/etnaviv: Use dma_buf from GEM object instance" Revert "drm/prime: Use dma_buf from GEM object instance" Revert "drm/gem-framebuffer: Use dma_buf from GEM object instance" Revert "drm/gem-shmem: Use dma_buf from GEM object instance" Revert "drm/gem-dma: Use dma_buf from GEM object instance"
drivers/gpu/drm/drm_gem_dma_helper.c | 2 +- drivers/gpu/drm/drm_gem_framebuffer_helper.c | 8 ++++++-- drivers/gpu/drm/drm_gem_shmem_helper.c | 4 ++-- drivers/gpu/drm/drm_prime.c | 8 +++++++- drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c | 4 ++-- drivers/gpu/drm/virtio/virtgpu_prime.c | 5 +++-- drivers/gpu/drm/vmwgfx/vmwgfx_gem.c | 6 +++--- 7 files changed, 24 insertions(+), 13 deletions(-)
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 1/7 Revert "drm/virtio: Use dma_buf from GEM object instance"
This reverts commit 415cb45895f43015515473fbc40563ca5eec9a7c.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/virtio/virtgpu_prime.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
drivers/gpu/drm/virtio/virtgpu_prime.c +3 -2
@@ -204,15 +204,16 @@ static void virtgpu_dma_buf_free_obj(struct drm_gem_object *obj) {struct virtio_gpu_object *bo =gem_to_virtio_gpu_obj (obj);struct virtio_gpu_device *vgdev = obj->dev->dev_private; +struct dma_buf_attachment *attach = obj->import_attach;if (drm_gem_is_imported (obj)) { -struct dma_buf *dmabuf = bo->dma_buf; +struct dma_buf *dmabuf = attach->dmabuf;dma_resv_lock (dmabuf->resv,NULL );virtgpu_dma_buf_unmap (bo);dma_resv_unlock (dmabuf->resv); -dma_buf_detach (dmabuf, obj->import_attach); +dma_buf_detach (dmabuf, attach);dma_buf_put (dmabuf); }
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 2/7 Revert "drm/vmwgfx: Use dma_buf from GEM object instance"
In reply to Thomas ZimmermannThis reverts commit aec8a40228acb385d60feec59b54573d307e60f3.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/vmwgfx/vmwgfx_gem.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/gpu/drm/vmwgfx/vmwgfx_gem.c +3 -3
@@ -85,10 +85,10 @@ static int vmw_gem_vmap(struct drm_gem_object *obj, struct iosys_map *map)int ret;if (drm_gem_is_imported (obj)) { - ret =dma_buf_vmap (obj->dma_buf, map); + ret =dma_buf_vmap (obj->import_attach->dmabuf, map);if (!ret) {if (drm_WARN_ON (obj->dev, map->is_iomem)) { -dma_buf_vunmap (obj->dma_buf, map); +dma_buf_vunmap (obj->import_attach->dmabuf, map);return -EIO ; } }
@@ -102,7 +102,7 @@ static int vmw_gem_vmap(struct drm_gem_object *obj, struct iosys_map *map)static void vmw_gem_vunmap (struct drm_gem_object *obj,struct iosys_map *map) {if (drm_gem_is_imported (obj)) -dma_buf_vunmap (obj->dma_buf, map); +dma_buf_vunmap (obj->import_attach->dmabuf, map);else drm_gem_ttm_vunmap (obj, map); }
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 3/7 Revert "drm/etnaviv: Use dma_buf from GEM object instance"
In reply to Thomas ZimmermannThis reverts commit e91eb3ae415472b28211d7fed07fa283845b311e.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c +2 -2
@@ -65,7 +65,7 @@ static void etnaviv_gem_prime_release(struct etnaviv_gem_object *etnaviv_obj)struct iosys_map map =IOSYS_MAP_INIT_VADDR (etnaviv_obj->vaddr);if (etnaviv_obj->vaddr) -dma_buf_vunmap_unlocked (etnaviv_obj->base.dma_buf, &map); +dma_buf_vunmap_unlocked (etnaviv_obj->base.import_attach->dmabuf, &map);/* Don't drop the pages for imported dmabuf, as they are not * ours, just free the array we allocated:
@@ -82,7 +82,7 @@ static void *etnaviv_gem_prime_vmap_impl(struct etnaviv_gem_object *etnaviv_obj)lockdep_assert_held (&etnaviv_obj->lock); - ret =dma_buf_vmap (etnaviv_obj->base.dma_buf, &map); + ret =dma_buf_vmap (etnaviv_obj->base.import_attach->dmabuf, &map);if (ret)return NULL ;return map.vaddr;
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 4/7 Revert "drm/prime: Use dma_buf from GEM object instance"
In reply to Thomas ZimmermannThis reverts commit f83a9b8c7fd0557b0c50784bfdc1bbe9140c9bf8.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/drm_prime.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/drm_prime.c +7 -1
@@ -453,7 +453,13 @@ struct dma_buf *drm_gem_prime_handle_to_dmabuf(struct drm_device *dev, }mutex_lock (&dev->object_name_lock); -/* re-export the original imported/exported object */ +/* re-export the original imported object */ +if (obj->import_attach) { + dmabuf = obj->import_attach->dmabuf; +get_dma_buf (dmabuf); + goto out_have_obj; + } +if (obj->dma_buf) {get_dma_buf (obj->dma_buf); dmabuf = obj->dma_buf;
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 5/7 Revert "drm/gem-framebuffer: Use dma_buf from GEM object instance"
In reply to Thomas ZimmermannThis reverts commit cce16fcd7446dcff7480cd9d2b6417075ed81065.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/drm_gem_framebuffer_helper.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
drivers/gpu/drm/drm_gem_framebuffer_helper.c +6 -2
@@ -420,6 +420,7 @@ EXPORT_SYMBOL(drm_gem_fb_vunmap);static void __drm_gem_fb_end_cpu_access (struct drm_framebuffer *fb,enum dma_data_direction dir,unsigned int num_planes) { +struct dma_buf_attachment *import_attach;struct drm_gem_object *obj;int ret;
@@ -428,9 +429,10 @@ static void __drm_gem_fb_end_cpu_access(struct drm_framebuffer *fb, enum dma_dat obj =drm_gem_fb_get_obj (fb, num_planes);if (!obj)continue ; + import_attach = obj->import_attach;if (!drm_gem_is_imported (obj))continue ; - ret =dma_buf_end_cpu_access (obj->dma_buf, dir); + ret =dma_buf_end_cpu_access (import_attach->dmabuf, dir);if (ret)drm_err (fb->dev,"dma_buf_end_cpu_access(%u, %d) failed: %d\n" , ret, num_planes, dir);
@@ -453,6 +455,7 @@ static void __drm_gem_fb_end_cpu_access(struct drm_framebuffer *fb, enum dma_dat*/ int drm_gem_fb_begin_cpu_access (struct drm_framebuffer *fb,enum dma_data_direction dir) { +struct dma_buf_attachment *import_attach;struct drm_gem_object *obj;unsigned int i;int ret;
@@ -463,9 +466,10 @@ int drm_gem_fb_begin_cpu_access(struct drm_framebuffer *fb, enum dma_data_direct ret = -EINVAL ; goto err___drm_gem_fb_end_cpu_access; } + import_attach = obj->import_attach;if (!drm_gem_is_imported (obj))continue ; - ret =dma_buf_begin_cpu_access (obj->dma_buf, dir); + ret =dma_buf_begin_cpu_access (import_attach->dmabuf, dir);if (ret) goto err___drm_gem_fb_end_cpu_access; }
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 6/7 Revert "drm/gem-shmem: Use dma_buf from GEM object instance"
In reply to Thomas ZimmermannThis reverts commit 1a148af06000e545e714fe3210af3d77ff903c11.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/drm_gem_shmem_helper.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/drm_gem_shmem_helper.c +2 -2
@@ -351,7 +351,7 @@ int drm_gem_shmem_vmap_locked(struct drm_gem_shmem_object *shmem,dma_resv_assert_held (obj->resv);if (drm_gem_is_imported (obj)) { - ret =dma_buf_vmap (obj->dma_buf, map); + ret =dma_buf_vmap (obj->import_attach->dmabuf, map); }else {pgprot_t prot =PAGE_KERNEL ;
@@ -413,7 +413,7 @@ void drm_gem_shmem_vunmap_locked(struct drm_gem_shmem_object *shmem,dma_resv_assert_held (obj->resv);if (drm_gem_is_imported (obj)) { -dma_buf_vunmap (obj->dma_buf, map); +dma_buf_vunmap (obj->import_attach->dmabuf, map); }else {dma_resv_assert_held (shmem->base.resv);
Signature · 1 line
2.50.0
Thomas Zimmermann
maintainerPATCH v2 7/7 Revert "drm/gem-dma: Use dma_buf from GEM object instance"
In reply to Thomas ZimmermannThis reverts commit e8afa1557f4f963c9a511bd2c6074a941c308685.
The dma_buf field in struct drm_gem_object is not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.
Workarounds in commit 5307dce878d4 ("drm/gem: Acquire references on GEM handles for framebuffers") and commit f6bfc9afc751 ("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.
Hence, this revert to going back to using .import_attach->dmabuf.
--- drivers/gpu/drm/drm_gem_dma_helper.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/drm_gem_dma_helper.c +1 -1
@@ -230,7 +230,7 @@ void drm_gem_dma_free(struct drm_gem_dma_object *dma_obj)if (drm_gem_is_imported (gem_obj)) {if (dma_obj->vaddr) -dma_buf_vunmap_unlocked (gem_obj->dma_buf, &map); +dma_buf_vunmap_unlocked (gem_obj->import_attach->dmabuf, &map);drm_prime_gem_destroy (gem_obj, dma_obj->sgt); }else if (dma_obj->vaddr) {if (dma_obj->map_noncoherent)
Signature · 1 line
2.50.0
If it helps Acked-by: Christian König <[email protected]> for the entire series.
Regards,
Christian.
Quoted 37 lines · Thomas Zimmermann
Revert the use of drm_gem_object.dma_buf back to .import_attach->dmabuf in the affected places. Separates references to imported and exported DMA bufs within a GEM object; as before.
The
dma_buffield in structdrm_gem_objectis not stable over the object instance's lifetime. The field becomes NULL when user space releases the final GEM handle on the buffer object. This resulted in a NULL-pointer deref.Workarounds in commit
5307dce878d4("drm/gem: Acquire references on GEM handles for framebuffers") and commitf6bfc9afc751("drm/framebuffer:
Acquire internal references on GEM handles") only solved the problem partially. They especially don't work for buffer objects without a DRM framebuffer associated.v2:
- extended commit messages (Sima)
- drop the GEM-handle changes to be resolved separatelyThomas Zimmermann (7):
Revert "drm/virtio: Usedma_buffrom GEM object instance" Revert "drm/vmwgfx: Usedma_buffrom GEM object instance" Revert "drm/etnaviv: Usedma_buffrom GEM object instance" Revert "drm/prime: Usedma_buffrom GEM object instance" Revert "drm/gem-framebuffer: Usedma_buffrom GEM object instance" Revert "drm/gem-shmem: Usedma_buffrom GEM object instance" Revert "drm/gem-dma: Usedma_buffrom GEM object instance"drivers/gpu/drm/drm_gem_dma_helper.c | 2 +- drivers/gpu/drm/drm_gem_framebuffer_helper.c | 8 ++++++-- drivers/gpu/drm/drm_gem_shmem_helper.c | 4 ++-- drivers/gpu/drm/drm_prime.c | 8 +++++++- drivers/gpu/drm/etnaviv/etnaviv_gem_prime.c | 4 ++-- drivers/gpu/drm/virtio/virtgpu_prime.c | 5 +++-- drivers/gpu/drm/vmwgfx/vmwgfx_gem.c | 6 +++--- 7 files changed, 24 insertions(+), 13 deletions(-)
Patchwork
CI✓ i915.CI.BAT: success for drm: Revert general use of struct drm_gem_object.dma_buf (rev2)
In reply to Thomas Zimmermann== Series Details ==
== Series Details ==
Series: drm: Revert general use of struct drm_gem_object.dma_buf (rev2)
URL : https://patchwork.freedesktop.org/series/151494/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_16864 -> Patchwork_151494v2
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/index.html
Participating hosts (44 -> 44)
------------------------------
Additional (1): fi-glk-j4005
Missing (1): fi-snb-2520m
Known issues
------------
Here are the changes found in Patchwork_151494v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@dmabuf@all-tests:
- bat-apl-1: [PASS][1] -> [ABORT][2] ([i915#12904]) +1 other test abort
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-apl-1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-apl-1/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- fi-glk-j4005: NOTRUN -> [SKIP][3] ([i915#2190])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/fi-glk-j4005/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-engines:
- fi-glk-j4005: NOTRUN -> [SKIP][4] ([i915#4613]) +3 other tests skip
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/fi-glk-j4005/igt@[email protected]
* igt@i915_selftest@live@workarounds:
- bat-dg2-14: [PASS][5] -> [DMESG-FAIL][6] ([i915#12061]) +1 other test dmesg-fail
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-dg2-14/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-dg2-14/igt@i915_selftest@[email protected]
* igt@kms_psr@psr-primary-page-flip:
- fi-glk-j4005: NOTRUN -> [SKIP][7] +11 other tests skip
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/fi-glk-j4005/igt@[email protected]
#### Possible fixes ####
* igt@gem_exec_fence@basic-await@vecs0:
- bat-rpls-4: [DMESG-WARN][8] ([i915#13400]) -> [PASS][9] +2 other tests pass
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-rpls-4/igt@gem_exec_fence@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-rpls-4/igt@gem_exec_fence@[email protected]
* igt@i915_selftest@live:
- bat-jsl-1: [DMESG-FAIL][10] ([i915#13774]) -> [PASS][11] +1 other test pass
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-jsl-1/igt@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-jsl-1/igt@[email protected]
* igt@i915_selftest@live@workarounds:
- bat-arls-5: [DMESG-FAIL][12] ([i915#12061]) -> [PASS][13] +1 other test pass
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-arls-5/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-arls-5/igt@i915_selftest@[email protected]
- bat-mtlp-6: [DMESG-FAIL][14] ([i915#12061]) -> [PASS][15] +1 other test pass
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-mtlp-6/igt@i915_selftest@[email protected]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-mtlp-6/igt@i915_selftest@[email protected]
- bat-arls-6: [DMESG-FAIL][16] ([i915#12061]) -> [PASS][17] +1 other test pass
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-arls-6/igt@i915_selftest@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-arls-6/igt@i915_selftest@[email protected]
#### Warnings ####
* igt@i915_selftest@live:
- bat-atsm-1: [DMESG-FAIL][18] ([i915#12061] / [i915#14204]) -> [DMESG-FAIL][19] ([i915#12061] / [i915#13929])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-atsm-1/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-atsm-1/igt@[email protected]
* igt@i915_selftest@live@mman:
- bat-atsm-1: [DMESG-FAIL][20] ([i915#14204]) -> [DMESG-FAIL][21] ([i915#13929])
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16864/bat-atsm-1/igt@i915_selftest@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/bat-atsm-1/igt@i915_selftest@[email protected]
[i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
[i915#12904]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12904
[i915#13400]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13400
[i915#13774]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13774
[i915#13929]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13929
[i915#14204]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14204
[i915#2190]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/2190
[i915#4613]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/4613
Build changes
-------------
* Linux: CI_DRM_16864 -> Patchwork_151494v2
CI-20190529: 20190529
CI_DRM_16864: b012f04b5be909a307ff629b297387e0ed55195a @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_8457: 756ebdbf0e4c75f0680c0a36db206a9f6ff126ce @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_151494v2: b012f04b5be909a307ff629b297387e0ed55195a @ git://anongit.freedesktop.org/gfx-ci/linux
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_151494v2/index.html