DGFX mmap with rpm
Subsystems (2)
cover DGFX mmap with rpm
As per PCIe Spec Section 5.3.1.4.1
When pcie function is in d3hot state,
Configuration and Message requests are the only TLPs accepted by a Function in the D3hot state. All other received Requests must be handled as Unsupported Requests, and all received Completions may optionally be handled as Unexpected Completions.
Therefore when gfx endpoint function is in d3 state, all pcie iomem transaction requires to transition the pcie function in D0 state.
RFC proposal to get community feedback to handle the lmem mmap memory mappings with runtime suspend.
Anshuman Gupta (2):
drm/i915/dgfx: Release mmap on rpm suspend drm/i915/dgfx: Runtime resume the dgpu on user fault
drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 29 +++++++++++++++++++----- drivers/gpu/drm/i915/gt/intel_gt.c | 1 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 2 ++ drivers/gpu/drm/i915/i915_gem.c | 6 +++++ 4 files changed, 32 insertions(+), 6 deletions(-)
Signature · 1 line
2.26.2
RFC 1/2 drm/i915/dgfx: Release mmap on rpm suspend
Release all mmap mapping for all lmem objects which are associated with userfault such that, while pcie function in D3hot, any access to memory mappings will raise a userfault.
--- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++ drivers/gpu/drm/i915/gt/intel_gt.c | 1 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 2 ++ drivers/gpu/drm/i915/i915_gem.c | 6 ++++++ 4 files changed, 13 insertions(+)
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +4 -0
@@ -1073,6 +1073,10 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf) }else { ret =ttm_bo_vm_dummy_page (vmf, vmf->vma->vm_page_prot); } + +if (i915_gem_object_is_lmem (obj)) +list_add (&obj->userfault_link, &to_gt (to_i915 (obj->base.dev))->lmem_userfault_list); +if (ret ==VM_FAULT_RETRY && !(vmf->flags &FAULT_FLAG_RETRY_NOWAIT ))return ret;
drivers/gpu/drm/i915/gt/intel_gt.c +1 -0
@@ -39,6 +39,7 @@ static void __intel_gt_init_early(struct intel_gt *gt) {spin_lock_init (>->irq_lock); +INIT_LIST_HEAD (>->lmem_userfault_list);INIT_LIST_HEAD (>->closed_vma);spin_lock_init (>->closed_lock);
drivers/gpu/drm/i915/gt/intel_gt_types.h +2 -0
@@ -132,6 +132,8 @@ struct intel_gt {struct intel_wakeref wakeref;atomic_t user_wakeref; +struct list_head lmem_userfault_list; +struct list_head closed_vma;spinlock_t closed_lock;/* guards the list of closed_vma */
drivers/gpu/drm/i915/i915_gem.c +6 -0
@@ -842,6 +842,12 @@ void i915_gem_runtime_suspend(struct drm_i915_private *i915) &to_gt(i915)->ggtt->userfault_list, userfault_link)__i915_gem_object_release_mmap_gtt (obj); +list_for_each_entry_safe (obj, on, + &to_gt (i915)->lmem_userfault_list, userfault_link) { +i915_gem_object_release_mmap_offset (obj); +list_del (&obj->userfault_link); + } +/* * The fence will be lost when the device powers down. If any were * in use by hardware (i.e. they are pinned), we should not be powering
Signature · 1 line
2.26.2
Re: [Intel-gfx] [RFC 1/2] drm/i915/dgfx: Release mmap on rpm suspend
Quoted 19 lines · Anshuman Gupta
Release all mmap mapping for all lmem objects which are associated with userfault such that, while pcie function in D3hot, any access to memory mappings will raise a userfault.
Cc Matthew Auld <[email protected]>Cc Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 4 ++++ drivers/gpu/drm/i915/gt/intel_gt.c | 1 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 2 ++ drivers/gpu/drm/i915/i915_gem.c | 6 ++++++ 4 files changed, 13 insertions(+)drivers/gpu/drm/i915/gem/i915_gem_ttm.c +0
-0
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault *vmf) · line 1078
Quoted 6 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +3
-0@@ -1073,6 +1073,10 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf) }else { ret =ttm_bo_vm_dummy_page (vmf, vmf->vma->vm_page_prot); } + +if (i915_gem_object_is_lmem (obj)) +list_add (&obj->userfault_link, &to_gt (to_i915 (obj->base.dev))->lmem_userfault_list);
Both patches need to be squashed together I think. Also AFAIK we need some kind of lock here to protect against concurrent list_add(). We also need something to prevent against double list_add(). And we should probably first check the ret value before touching the list.
Quoted 46 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0+if (ret ==VM_FAULT_RETRY && !(vmf->flags &FAULT_FLAG_RETRY_NOWAIT ))return ret;drivers/gpu/drm/i915/gt/intel_gt.c +1
-0@@ -39,6 +39,7 @@ static void __intel_gt_init_early(struct intel_gt *gt) {spin_lock_init (>->irq_lock); +INIT_LIST_HEAD (>->lmem_userfault_list);INIT_LIST_HEAD (>->closed_vma);spin_lock_init (>->closed_lock);drivers/gpu/drm/i915/gt/intel_gt_types.h +2
-0@@ -132,6 +132,8 @@ struct intel_gt {struct intel_wakeref wakeref;atomic_t user_wakeref; +struct list_head lmem_userfault_list; +struct list_head closed_vma;spinlock_t closed_lock;/* guards the list of closed_vma */ drivers/gpu/drm/i915/i915_gem.c +6
-0@@ -842,6 +842,12 @@ void i915_gem_runtime_suspend(struct drm_i915_private *i915) &to_gt(i915)->ggtt->userfault_list, userfault_link)__i915_gem_object_release_mmap_gtt (obj); +list_for_each_entry_safe (obj, on, + &to_gt (i915)->lmem_userfault_list, userfault_link) { +i915_gem_object_release_mmap_offset (obj); +list_del (&obj->userfault_link); + } +/* * The fence will be lost when the device powers down. If any were * in use by hardware (i.e. they are pinned), we should not be powering
RFC 2/2 drm/i915/dgfx: Runtime resume the dgpu on user fault
In reply to Anshuman GuptaRuntime resume the dgpu(when gem object lies in lmem). This will transition the dgpu graphics function to D0 state if it was in D3 in order to access the mmap memory mappings.
--- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-)
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +19 -6
@@ -1020,6 +1020,7 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)struct ttm_buffer_object *bo = area->vm_private_data;struct drm_device *dev = bo->base.dev;struct drm_i915_gem_object *obj; +intel_wakeref_t wakeref =0 ;vm_fault_t ret;int idx;
@@ -1027,18 +1028,24 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)if (!obj)return VM_FAULT_SIGBUS ; +if (i915_gem_object_is_lmem (obj)) + wakeref =intel_runtime_pm_get (&to_i915 (obj->base.dev)->runtime_pm); +/* Sanity check that we allow writing into this object */ if (unlikely (i915_gem_object_is_readonly (obj) && - area->vm_flags &VM_WRITE )) -return VM_FAULT_SIGBUS ; + area->vm_flags &VM_WRITE )) { + ret =VM_FAULT_SIGBUS ; + goto out_rpm; + } ret =ttm_bo_vm_reserve (bo, vmf);if (ret) -return ret; + goto out_rpm;if (obj->mm.madv !=I915_MADV_WILLNEED ) {dma_resv_unlock (bo->base.resv); -return VM_FAULT_SIGBUS ; + ret =VM_FAULT_SIGBUS ; + goto out_rpm; }if (!i915_ttm_resource_mappable (bo->resource)) {
@@ -1062,7 +1069,8 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)if (err) {drm_dbg (dev,"Unable to make resource CPU accessible\n" );dma_resv_unlock (bo->base.resv); -return VM_FAULT_SIGBUS ; + ret =VM_FAULT_SIGBUS ; + goto out_rpm; } }
@@ -1078,11 +1086,16 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)list_add (&obj->userfault_link, &to_gt (to_i915 (obj->base.dev))->lmem_userfault_list);if (ret ==VM_FAULT_RETRY && !(vmf->flags &FAULT_FLAG_RETRY_NOWAIT )) -return ret; + goto out_rpm;i915_ttm_adjust_lru (obj);dma_resv_unlock (bo->base.resv); + +out_rpm: +if (wakeref) +intel_runtime_pm_put (&to_i915 (obj->base.dev)->runtime_pm, wakeref); +return ret; }
Signature · 1 line
2.26.2
Re: [Intel-gfx] [RFC 2/2] drm/i915/dgfx: Runtime resume the dgpu on user fault
Quoted 25 lines · Anshuman Gupta
Runtime resume the dgpu(when gem object lies in lmem). This will transition the dgpu graphics function to D0 state if it was in D3 in order to access the mmap memory mappings.
Cc Matthew Auld <[email protected]>Cc Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 25 +++++++++++++++++++------ 1 file changed, 19 insertions(+), 6 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0@@ -1020,6 +1020,7 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)struct ttm_buffer_object *bo = area->vm_private_data;struct drm_device *dev = bo->base.dev;struct drm_i915_gem_object *obj; +intel_wakeref_t wakeref =0 ;vm_fault_t ret;int idx;
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault *vmf) · line 1031
Quoted 4 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0@@ -1027,18 +1028,24 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)if (!obj)return VM_FAULT_SIGBUS ; +if (i915_gem_object_is_lmem (obj))
We shouldn't call this without first locking the object (see bo_vm_reserve below), since it could be in the process of being moved to system memory or vice versa. For example, below we check is_lmem() again (this time with the lock held), which might return true, even though here it returned false, which means we can now race against the i915_gem_runtime_suspend() modifying the list as we add something.
We ofc still need to audit all the kernel internal users that are touching lmem though a CPU mapping, and making sure we have the right pm_get/put wrapping those accesses.
Quoted 38 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +11
-5+ wakeref =intel_runtime_pm_get (&to_i915 (obj->base.dev)->runtime_pm); +/* Sanity check that we allow writing into this object */ if (unlikely (i915_gem_object_is_readonly (obj) && - area->vm_flags &VM_WRITE )) -return VM_FAULT_SIGBUS ; + area->vm_flags &VM_WRITE )) { + ret =VM_FAULT_SIGBUS ; + goto out_rpm; + } ret =ttm_bo_vm_reserve (bo, vmf);if (ret) -return ret; + goto out_rpm;if (obj->mm.madv !=I915_MADV_WILLNEED ) {dma_resv_unlock (bo->base.resv); -return VM_FAULT_SIGBUS ; + ret =VM_FAULT_SIGBUS ; + goto out_rpm; }if (!i915_ttm_resource_mappable (bo->resource)) {@@ -1062,7 +1069,8 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)if (err) {drm_dbg (dev,"Unable to make resource CPU accessible\n" );dma_resv_unlock (bo->base.resv); -return VM_FAULT_SIGBUS ; + ret =VM_FAULT_SIGBUS ; + goto out_rpm; } }@@ -1078,11 +1086,16 @@ static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)list_add (&obj->userfault_link, &to_gt (to_i915 (obj->base.dev))->lmem_userfault_list);if (ret ==VM_FAULT_RETRY && !(vmf->flags &FAULT_FLAG_RETRY_NOWAIT ))
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault *vmf) · line 1097
Quoted 10 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +5
-1-return ret; + goto out_rpm;i915_ttm_adjust_lru (obj);dma_resv_unlock (bo->base.resv); + +out_rpm: +if (wakeref) +intel_runtime_pm_put (&to_i915 (obj->base.dev)->runtime_pm, wakeref);
Do we need something like DRM_I915_USERFAULT_AUTOSUSPEND here?
Quoted 4 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0+return ret; }
Re: [Intel-gfx] [RFC 2/2] drm/i915/dgfx: Runtime resume the dgpu on user fault
Quoted 43 lines
-----Original Message-----
From: Auld, Matthew <[email protected]>
Sent: Wednesday, August 17, 2022 11:41 PM
To: Gupta, Anshuman <[email protected]>; intel- [email protected]
Cc: [email protected]; Vivi, Rodrigo <[email protected]>; Nilawar, Badal <[email protected]>; [email protected]
Subject: Re: [RFC 2/2] drm/i915/dgfx: Runtime resume the dgpu on user faultQuoted 9 lines · Anshuman Gupta
Runtime resume the dgpu(when gem object lies in lmem). This will transition the dgpu graphics function to D0 state if it was in D3 in order to access the mmap memory mappings.
Cc Matthew Auld <[email protected]>Cc Rodrigo Vivi <[email protected]>Signed-off-by Anshuman Gupta <[email protected]>--- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 25 +++++++++++++++++++------
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault
Quoted 8 lines
1 file changed, 19 insertions(+), 6 deletions(-)drivers/gpu/drm/i915/gem/i915_gem_ttm.c +0
-0@@ -1020,6 +1020,7 @@ static vm_fault_t vm_fault_ttm(struct vm_fault*vmf)
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault
Quoted 8 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0struct ttm_buffer_object *bo = area->vm_private_data;struct drm_device *dev = bo->base.dev;struct drm_i915_gem_object *obj; +intel_wakeref_t wakeref =0 ;vm_fault_t ret;int idx;@@ -1027,18 +1028,24 @@ static vm_fault_t vm_fault_ttm(struct vm_fault*vmf)
Quoted 3 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +0
-0if (!obj)return VM_FAULT_SIGBUS ;
Quoted 8 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault *vmf) · line 1031
Quoted 1 line
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0+if (i915_gem_object_is_lmem (obj))We shouldn't call this without first locking the object (see
bo_vm_reservebelow), since it could be in the process of being moved to system memory or vice versa. For example, below we checkis_lmem()again (this time with the lock held), which might return true, even though here it returned false, which means we can now race against thei915_gem_runtime_suspend()modifying the list as we add something.
Thanks for review, i will fix this.
Quoted 4 lines
We ofc still need to audit all the kernel internal users that are touching lmem though a CPU mapping, and making sure we have the right pm_get/put wrapping those accesses.
I was thinking to use assert_rpm_wakelock_held in i915_gem_object_pin_map() So every caller should take the proper wakeref before mapping the pages. It will be difficult to track the wakeref with multiple i915_gem_object_{pin,unpin}_map.
And i915_ttm_move_memcpy() also need to wrapped with rpm get/put.
Other than that is there are any iomem related pcie transaction transaction involved to prepare object sgl page list ?
Thanks,
Anshuman Gupta.
Quoted 62 lines
Quoted 26 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +10
-4+ wakeref = +intel_runtime_pm_get (&to_i915 (obj->base.dev)->runtime_pm); +/* Sanity check that we allow writing into this object */ if (unlikely (i915_gem_object_is_readonly (obj) && - area->vm_flags &VM_WRITE )) -return VM_FAULT_SIGBUS ; + area->vm_flags &VM_WRITE )) { + ret =VM_FAULT_SIGBUS ; + goto out_rpm; + } ret =ttm_bo_vm_reserve (bo, vmf);if (ret) -return ret; + goto out_rpm;if (obj->mm.madv !=I915_MADV_WILLNEED ) {dma_resv_unlock (bo->base.resv); -return VM_FAULT_SIGBUS ; + ret =VM_FAULT_SIGBUS ; + goto out_rpm; } if (!i915_ttm_resource_mappable(bo->resource)) { @@ -1062,7 +1069,8Quoted 3 lines
@@ static
vm_fault_tvm_fault_ttm(struct vm_fault *vmf)
if (err) {
drm_dbg(dev, "Unable to make resource CPUaccessible\n");
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault
Quoted 8 lines
dma_resv_unlock(bo->base.resv);drivers/gpu/drm/i915/gem/i915_gem_ttm.c +2
-1-return VM_FAULT_SIGBUS ; + ret =VM_FAULT_SIGBUS ; + goto out_rpm; } }@@ -1078,11 +1086,16 @@ static vm_fault_t vm_fault_ttm(struct vm_fault*vmf)
drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault · line 1089
Quoted 4 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +0
-0list_add (&obj->userfault_link, &to_gt (to_i915 (obj->base.dev))->lmem_userfault_list); if (ret == VM_FAULT_RETRY && !(vmf->flags &
FAULT_FLAG_RETRY_NOWAIT))drivers/gpu/drm/i915/gem/i915_gem_ttm.c static vm_fault_t vm_fault_ttm(struct vm_fault *vmf)
Quoted 10 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +5
-1-return ret; + goto out_rpm;i915_ttm_adjust_lru (obj);dma_resv_unlock (bo->base.resv); + +out_rpm: +if (wakeref) + intel_runtime_pm_put(&to_i915(obj->base.dev)->runtime_pm,wakeref);
Do we need something like
DRM_I915_USERFAULT_AUTOSUSPENDhere?Quoted 4 lines
drivers/gpu/drm/i915/gem/i915_gem_ttm.c +1
-0+return ret; }
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for DGFX mmap with rpm
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: DGFX mmap with rpm
URL : https://patchwork.freedesktop.org/series/107400/
State : warning
== Summary ==
Error: dim sparse failed
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for DGFX mmap with rpm
In reply to Anshuman Gupta== Series Details ==
== Series Details ==
Series: DGFX mmap with rpm
URL : https://patchwork.freedesktop.org/series/107400/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11993 -> Patchwork_107400v1
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_107400v1 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_107400v1, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/index.html
Participating hosts (31 -> 34)
------------------------------
Additional (3): fi-icl-u2 fi-tgl-dsi bat-adlp-4
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_107400v1:
### IGT changes ###
#### Possible regressions ####
* igt@gem_busy@busy@all:
- bat-dg1-6: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11993/bat-dg1-6/igt@gem_busy@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/bat-dg1-6/igt@gem_busy@[email protected]
- bat-dg1-5: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11993/bat-dg1-5/igt@gem_busy@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/bat-dg1-5/igt@gem_busy@[email protected]
* igt@i915_module_load@load:
- fi-icl-u2: NOTRUN -> [DMESG-WARN][5]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/fi-icl-u2/igt@[email protected]
- bat-adlp-4: NOTRUN -> [DMESG-WARN][6]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/bat-adlp-4/igt@[email protected]
* igt@i915_suspend@basic-s3-without-i915:
- fi-pnv-d510: NOTRUN -> [INCOMPLETE][7]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/fi-pnv-d510/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_107400v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@kms_flip@basic-flip-vs-wf_vblank@b-vga1:
- fi-pnv-d510: [PASS][8] -> [FAIL][9] ([i915#2122])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11993/fi-pnv-d510/igt@kms_flip@[email protected]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/fi-pnv-d510/igt@kms_flip@[email protected]
* igt@runner@aborted:
- bat-adlp-4: NOTRUN -> [FAIL][10] ([i915#4312])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/bat-adlp-4/igt@[email protected]
- fi-icl-u2: NOTRUN -> [FAIL][11] ([i915#4312])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/fi-icl-u2/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@requests:
- fi-pnv-d510: [DMESG-FAIL][12] ([i915#4528]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_11993/fi-pnv-d510/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/fi-pnv-d510/igt@i915_selftest@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1245]: https://gitlab.freedesktop.org/drm/intel/issues/1245
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#3301]: https://gitlab.freedesktop.org/drm/intel/issues/3301
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4528]: https://gitlab.freedesktop.org/drm/intel/issues/4528
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#6559]: https://gitlab.freedesktop.org/drm/intel/issues/6559
[i915#6596]: https://gitlab.freedesktop.org/drm/intel/issues/6596
Build changes
-------------
* Linux: CI_DRM_11993 -> Patchwork_107400v1
CI-20190529: 20190529
CI_DRM_11993: 2dfc67084761ba9b6259873bd574548dc4827296 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_6629: d24e986fb3b2ab6d755498d27828bc85931d12ff @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_107400v1: 2dfc67084761ba9b6259873bd574548dc4827296 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
08e0d07fba36 drm/i915/dgfx: Runtime resume the dgpu on user fault 319f12d0972f drm/i915/dgfx: Release mmap on rpm suspend
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_107400v1/index.html