i915: dedicated MCR locking and hardware semaphore
Subsystems (2)
cover i915: dedicated MCR locking and hardware semaphore
We've been overloading uncore->lock to protect access to the MCR steering register. That's not really what uncore->lock is intended for, and it would be better if we didn't need to hold such a high-traffic spinlock for the whole sequence of (apply steering, access MCR register, restore steering). Switch to a dedicated MCR lock to protect the steering control register over this critical section and stop relying on the high-traffic uncore->lock. On pre-MTL platforms the dedicated MCR lock is just another software lock, but on MTL and beyond we also utilize the hardware-provided STEER_SEMAPHORE that allows us to synchronize with external hardware and firmware agents.
Matt Roper (4):
drm/i915/gt: Correct kerneldoc for intel_gt_mcr_wait_for_reg() drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes drm/i915/gt: Add dedicated MCR lock
drm/i915/mtl: Add hardware-level lock for steering
drivers/gpu/drm/i915/gt/intel_gt.c | 2 + drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 107 ++++++++++++++++++-- drivers/gpu/drm/i915/gt/intel_gt_mcr.h | 2 + drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 8 ++ drivers/gpu/drm/i915/gt/intel_mocs.c | 2 + drivers/gpu/drm/i915/gt/intel_workarounds.c | 4 + 7 files changed, 115 insertions(+), 11 deletions(-)
Signature · 1 line
2.38.1
PATCH 1/4 drm/i915/gt: Correct kerneldoc for intel_gt_mcr_wait_for_reg()
The kerneldoc function name was not updated when this function was converted to a non-fw form.
--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +1 -1
@@ -702,7 +702,7 @@ void intel_gt_mcr_get_ss_steering(struct intel_gt *gt, unsigned int dss, }/** -* intel_gt_mcr_wait_for_reg_fw - wait until MCR register matches expected state +* intel_gt_mcr_wait_for_reg - wait until MCR register matches expected state * @gt: GT structure * @reg: the register to read * @mask: mask to apply to register value
Signature · 1 line
2.38.1
PATCH 2/4 drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes
In reply to Matt RoperPassing the GT rather than uncore to the lowest level MCR read and write functions will make it easier to introduce dedicated MCR locking in a folling patch.
--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-)
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +10 -8
@@ -221,7 +221,7 @@ static i915_reg_t mcr_reg_cast(const i915_mcr_reg_t mcr)/* * rw_with_mcr_steering_fw - Access a register with specific MCR steering -* @uncore: pointer to struct intel_uncore +* @gt: GT to read register from * @reg: register being accessed * @rw_flag: FW_REG_READ for read access or FW_REG_WRITE for write access * @group: group number (documented as "sliceid" on older platforms)
@@ -232,10 +232,11 @@ static i915_reg_t mcr_reg_cast(const i915_mcr_reg_t mcr)* * Caller needs to make sure the relevant forcewake wells are up. */ -static u32 rw_with_mcr_steering_fw (struct intel_uncore *uncore, +static u32 rw_with_mcr_steering_fw (struct intel_gt *gt,i915_mcr_reg_t reg,u8 rw_flag,int group,int instance,u32 value) { +struct intel_uncore *uncore = gt->uncore;u32 mcr_mask, mcr_ss, mcr, old_mcr, val =0 ;lockdep_assert_held (&uncore->lock);
@@ -308,11 +309,12 @@ static u32 rw_with_mcr_steering_fw(struct intel_uncore *uncore,return val; } -static u32 rw_with_mcr_steering (struct intel_uncore *uncore, +static u32 rw_with_mcr_steering (struct intel_gt *gt,i915_mcr_reg_t reg,u8 rw_flag,int group,int instance,u32 value) { +struct intel_uncore *uncore = gt->uncore;enum forcewake_domains fw_domains;u32 val;
@@ -325,7 +327,7 @@ static u32 rw_with_mcr_steering(struct intel_uncore *uncore,spin_lock_irq (&uncore->lock);intel_uncore_forcewake_get__locked (uncore, fw_domains); - val =rw_with_mcr_steering_fw (uncore, reg, rw_flag, group, instance, value); + val =rw_with_mcr_steering_fw (gt, reg, rw_flag, group, instance, value);intel_uncore_forcewake_put__locked (uncore, fw_domains);spin_unlock_irq (&uncore->lock);
@@ -347,7 +349,7 @@ u32 intel_gt_mcr_read(struct intel_gt *gt,i915_mcr_reg_t reg, int group, int instance) { - return rw_with_mcr_steering(gt->uncore, reg, FW_REG_READ, group, instance, 0); + return rw_with_mcr_steering(gt, reg, FW_REG_READ, group, instance, 0); }/**
@@ -364,7 +366,7 @@ u32 intel_gt_mcr_read(struct intel_gt *gt,void intel_gt_mcr_unicast_write (struct intel_gt *gt,i915_mcr_reg_t reg,u32 value,int group,int instance) { -rw_with_mcr_steering (gt->uncore, reg,FW_REG_WRITE , group, instance, value); +rw_with_mcr_steering (gt, reg,FW_REG_WRITE , group, instance, value); }/**
@@ -588,7 +590,7 @@ u32 intel_gt_mcr_read_any_fw(struct intel_gt *gt, i915_mcr_reg_t reg)for (type =0 ; type <NUM_STEERING_TYPES ; type++) {if (reg_needs_read_steering (gt, reg, type)) {get_nonterminated_steering (gt, type, &group, &instance); -return rw_with_mcr_steering_fw (gt->uncore, reg, +return rw_with_mcr_steering_fw (gt, reg,FW_REG_READ , group, instance,0 ); }
@@ -615,7 +617,7 @@ u32 intel_gt_mcr_read_any(struct intel_gt *gt, i915_mcr_reg_t reg)for (type =0 ; type <NUM_STEERING_TYPES ; type++) {if (reg_needs_read_steering (gt, reg, type)) {get_nonterminated_steering (gt, type, &group, &instance); -return rw_with_mcr_steering (gt->uncore, reg, +return rw_with_mcr_steering (gt, reg,FW_REG_READ , group, instance,0 ); }
Signature · 1 line
2.38.1
PATCH 3/4 drm/i915/gt: Add dedicated MCR lock
In reply to Matt RoperWe've been overloading uncore->lock to protect access to the MCR steering register. That's not really what uncore->lock is intended for, and it would be better if we didn't need to hold such a high-traffic spinlock for the whole sequence of (apply steering, access MCR register, restore steering). Let's create a dedicated MCR lock to protect the steering control register over this critical section and stop relying on the high-traffic uncore->lock.
For now the new lock is a software lock. However some platforms (MTL and beyond) have a hardware-provided locking mechanism that can be used to serialize not only software accesses, but also hardware/firmware accesses as well; support for that hardware level lock will be added in a future patch.
--- drivers/gpu/drm/i915/gt/intel_gt.c | 2 + drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 66 ++++++++++++++++++++- drivers/gpu/drm/i915/gt/intel_gt_mcr.h | 2 + drivers/gpu/drm/i915/gt/intel_gt_types.h | 8 +++ drivers/gpu/drm/i915/gt/intel_mocs.c | 2 + drivers/gpu/drm/i915/gt/intel_workarounds.c | 4 ++ 6 files changed, 82 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/gt/intel_gt.c +2 -0
@@ -1094,6 +1094,7 @@ static void mmio_invalidate_full(struct intel_gt *gt)intel_uncore_forcewake_get (uncore,FORCEWAKE_ALL ); +intel_gt_mcr_lock (gt);spin_lock_irq (&uncore->lock);/* serialise invalidate with GT reset */ awake =0 ;
@@ -1129,6 +1130,7 @@ static void mmio_invalidate_full(struct intel_gt *gt)intel_uncore_write_fw (uncore,GEN12_OA_TLB_INV_CR ,1 );spin_unlock_irq (&uncore->lock); +intel_gt_mcr_unlock (gt);for_each_engine_masked (engine, gt, awake, tmp) {struct reg_and_bit rb;
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +64 -2
173 lines not on this page · raw message
drivers/gpu/drm/i915/gt/intel_gt_mcr.h +2 -0
@@ -9,6 +9,8 @@#include "intel_gt_types.h" void intel_gt_mcr_init (struct intel_gt *gt); +void intel_gt_mcr_lock (struct intel_gt *gt); +void intel_gt_mcr_unlock (struct intel_gt *gt); u32 intel_gt_mcr_read(struct intel_gt *gt, i915_mcr_reg_t reg,
drivers/gpu/drm/i915/gt/intel_gt_types.h +8 -0
@@ -233,6 +233,14 @@ struct intel_gt {u8 instanceid; } default_steering; +/** +* @mcr_lock: Protects the MCR steering register +* +* Protects the MCR steering register (e.g., GEN8_MCR_SELECTOR). +* Should be taken before uncore->lock in cases where both are desired. +*/ +spinlock_t mcr_lock; +/* * Base of per-tile GTTMMADR where we can derive the MMIO and the GGTT. */
drivers/gpu/drm/i915/gt/intel_mocs.c +2 -0
@@ -616,11 +616,13 @@ static void init_l3cc_table(struct intel_gt *gt,unsigned int i;u32 l3cc; +intel_gt_mcr_lock (gt);for_each_l3cc (l3cc, table, i)if (GRAPHICS_VER_FULL (gt->i915) >=IP_VER (12 ,50 ))intel_gt_mcr_multicast_write_fw (gt,XEHP_LNCFCMOCS (i), l3cc);else intel_uncore_write_fw (gt->uncore,GEN9_LNCFCMOCS (i), l3cc); +intel_gt_mcr_unlock (gt); }void intel_mocs_init_engine (struct intel_engine_cs *engine)
drivers/gpu/drm/i915/gt/intel_workarounds.c +4 -0
@@ -1752,6 +1752,7 @@ static void wa_list_apply(const struct i915_wa_list *wal) fw =wal_get_fw_for_rmw (uncore, wal); +intel_gt_mcr_lock (gt);spin_lock_irqsave (&uncore->lock, flags);intel_uncore_forcewake_get__locked (uncore, fw);
@@ -1782,6 +1783,7 @@ static void wa_list_apply(const struct i915_wa_list *wal)intel_uncore_forcewake_put__locked (uncore, fw);spin_unlock_irqrestore (&uncore->lock, flags); +intel_gt_mcr_unlock (gt); }void intel_gt_apply_workarounds (struct intel_gt *gt)
@@ -1802,6 +1804,7 @@ static bool wa_list_verify(struct intel_gt *gt, fw =wal_get_fw_for_rmw (uncore, wal); +intel_gt_mcr_lock (gt);spin_lock_irqsave (&uncore->lock, flags);intel_uncore_forcewake_get__locked (uncore, fw);
@@ -1813,6 +1816,7 @@ static bool wa_list_verify(struct intel_gt *gt,intel_uncore_forcewake_put__locked (uncore, fw);spin_unlock_irqrestore (&uncore->lock, flags); +intel_gt_mcr_unlock (gt);return ok; }
Signature · 1 line
2.38.1
PATCH 4/4 drm/i915/mtl: Add hardware-level lock for steering
In reply to Matt RoperStarting with MTL, the driver needs to not only protect the steering control register from simultaneous software accesses, but also protect against races with hardware/firmware agents. The hardware provides a dedicated locking mechanism to support this via the STEER_SEMAPHORE register. Reading the register acts as a 'trylock' operation; the read will return 0x1 if the lock is acquired or 0x0 if something else is already holding the lock; once acquired, writing 0x1 to the register will release the lock.
We'll continue to grab the software lock as well, just so lockdep can track our locking; assuming the hardware lock is behaving properly, there should never be any contention on the software lock in this case.
--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 29 +++++++++++++++++++++---- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + 2 files changed, 26 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +25 -4
@@ -345,10 +345,9 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @gt: GT structure * * Performs locking to protect the steering for the duration of an MCR -* operation. Depending on the platform, this may be a software lock -* (gt->mcr_lock) or a hardware lock (i.e., a register that synchronizes -* access not only for the driver, but also for external hardware and -* firmware agents). +* operation. On MTL and beyond, a hardware lock will also be taken to +* serialize access not only for the driver, but also for external hardware and +* firmware agents. * * Context: Takes gt->mcr_lock. uncore->lock should *not* be held when this * function is called, although it may be acquired after this
@@ -356,9 +355,28 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,*/ void intel_gt_mcr_lock (struct intel_gt *gt) { +int err =0 ; +lockdep_assert_not_held (>->uncore->lock); +/* +* Starting with MTL, we need to coordinate not only with other +* driver threads, but also with hardware/firmware agents. A dedicated +* locking register is used. +*/ +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) + err =wait_for (intel_uncore_read_fw (gt->uncore, +STEER_SEMAPHORE ) ==0x1 ,1 ); + +/* +* Even on platforms with a hardware lock, we'll continue to grab +* a software spinlock too for lockdep purposes. If the hardware lock +* was already acquired, there should never be contention on the +* software lock. +*/ spin_lock (>->mcr_lock); + +drm_WARN_ON_ONCE (>->i915->drm, err == -ETIMEDOUT ); }/**
@@ -372,6 +390,9 @@ void intel_gt_mcr_lock(struct intel_gt *gt)void intel_gt_mcr_unlock (struct intel_gt *gt) {spin_unlock (>->mcr_lock); + +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) +intel_uncore_write_fw (gt->uncore,STEER_SEMAPHORE ,0x1 ); }/**
drivers/gpu/drm/i915/gt/intel_gt_regs.h +1 -0
@@ -67,6 +67,7 @@#define GMD_ID_MEDIA _MMIO(MTL_MEDIA_GSI_BASE + 0xd8c)#define MCFG_MCR_SELECTOR _MMIO(0xfd0) +#define STEER_SEMAPHORE _MMIO(0xfd0)#define MTL_MCR_SELECTOR _MMIO(0xfd4)#define SF_MCR_SELECTOR _MMIO(0xfd8)#define GEN8_MCR_SELECTOR _MMIO(0xfdc)
Signature · 1 line
2.38.1
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for i915: dedicated MCR locking and hardware semaphore
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore
URL : https://patchwork.freedesktop.org/series/111220/
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 i915: dedicated MCR locking and hardware semaphore
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore
URL : https://patchwork.freedesktop.org/series/111220/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12418 -> Patchwork_111220v1
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_111220v1 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_111220v1, 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_111220v1/index.html
Participating hosts (33 -> 30)
------------------------------
Additional (2): bat-adls-5 fi-tgl-dsi
Missing (5): bat-dg1-6 bat-dg2-8 bat-adlp-6 bat-adln-1 bat-rplp-1
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_111220v1:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@execlists:
- fi-bdw-gvtdvm: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-bdw-gvtdvm/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bdw-gvtdvm/igt@i915_selftest@[email protected]
- fi-bsw-nick: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-bsw-nick/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bsw-nick/igt@i915_selftest@[email protected]
- fi-bsw-kefka: [PASS][5] -> [DMESG-WARN][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-bsw-kefka/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bsw-kefka/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@requests:
- fi-rkl-11600: [PASS][7] -> [DMESG-WARN][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-rkl-11600/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-rkl-11600/igt@i915_selftest@[email protected]
- fi-skl-6700k2: [PASS][9] -> [DMESG-WARN][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-skl-6700k2/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-skl-6700k2/igt@i915_selftest@[email protected]
- fi-cfl-8109u: [PASS][11] -> [DMESG-WARN][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-cfl-8109u/igt@i915_selftest@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-cfl-8109u/igt@i915_selftest@[email protected]
- fi-icl-u2: [PASS][13] -> [DMESG-WARN][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-icl-u2/igt@i915_selftest@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-icl-u2/igt@i915_selftest@[email protected]
- fi-apl-guc: NOTRUN -> [DMESG-WARN][15]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-apl-guc/igt@i915_selftest@[email protected]
- fi-glk-j4005: [PASS][16] -> [DMESG-WARN][17]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-glk-j4005/igt@i915_selftest@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-glk-j4005/igt@i915_selftest@[email protected]
- fi-skl-guc: [PASS][18] -> [DMESG-WARN][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-skl-guc/igt@i915_selftest@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-skl-guc/igt@i915_selftest@[email protected]
- fi-kbl-7567u: [PASS][20] -> [DMESG-WARN][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-kbl-7567u/igt@i915_selftest@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-kbl-7567u/igt@i915_selftest@[email protected]
- fi-cfl-8700k: [PASS][22] -> [DMESG-WARN][23]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-cfl-8700k/igt@i915_selftest@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-cfl-8700k/igt@i915_selftest@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_selftest@live@requests:
- {bat-adls-5}: NOTRUN -> [DMESG-WARN][24]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/bat-adls-5/igt@i915_selftest@[email protected]
- {bat-jsl-1}: [PASS][25] -> [DMESG-WARN][26]
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/bat-jsl-1/igt@i915_selftest@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/bat-jsl-1/igt@i915_selftest@[email protected]
- {fi-ehl-2}: [PASS][27] -> [DMESG-WARN][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-ehl-2/igt@i915_selftest@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-ehl-2/igt@i915_selftest@[email protected]
- {fi-tgl-dsi}: NOTRUN -> [DMESG-WARN][29]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-tgl-dsi/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_111220v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_lmem_swapping@basic:
- fi-apl-guc: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#4613]) +3 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-apl-guc/igt@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- fi-glk-j4005: [PASS][31] -> [DMESG-FAIL][32] ([i915#5334])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-glk-j4005/igt@i915_selftest@live@gt_heartbeat.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-glk-j4005/igt@i915_selftest@live@gt_heartbeat.html
* igt@runner@aborted:
- fi-skl-6700k2: NOTRUN -> [FAIL][33] ([i915#4312])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-skl-6700k2/igt@[email protected]
- fi-cfl-8109u: NOTRUN -> [FAIL][34] ([i915#4312])
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-cfl-8109u/igt@[email protected]
- fi-icl-u2: NOTRUN -> [FAIL][35] ([i915#4312])
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-icl-u2/igt@[email protected]
- fi-apl-guc: NOTRUN -> [FAIL][36] ([fdo#109271] / [i915#4312])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-apl-guc/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [FAIL][37] ([i915#4312])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-glk-j4005/igt@[email protected]
- fi-skl-guc: NOTRUN -> [FAIL][38] ([i915#4312])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-skl-guc/igt@[email protected]
- fi-kbl-7567u: NOTRUN -> [FAIL][39] ([i915#4312])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-kbl-7567u/igt@[email protected]
- fi-cfl-8700k: NOTRUN -> [FAIL][40] ([i915#4312])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-cfl-8700k/igt@[email protected]
- fi-bsw-nick: NOTRUN -> [FAIL][41] ([fdo#109271] / [i915#4312])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bsw-nick/igt@[email protected]
- fi-rkl-11600: NOTRUN -> [FAIL][42] ([i915#4312])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-rkl-11600/igt@[email protected]
- fi-bdw-gvtdvm: NOTRUN -> [FAIL][43] ([i915#4312])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bdw-gvtdvm/igt@[email protected]
- fi-bsw-kefka: NOTRUN -> [FAIL][44] ([fdo#109271] / [i915#4312])
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bsw-kefka/igt@[email protected]
#### Possible fixes ####
* igt@core_hotunplug@unbind-rebind:
- fi-apl-guc: [INCOMPLETE][45] ([i915#7073]) -> [PASS][46]
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-apl-guc/igt@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-apl-guc/igt@[email protected]
* igt@gem_exec_suspend@basic-s0@smem:
- {bat-rpls-2}: [DMESG-WARN][47] ([i915#6434]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/bat-rpls-2/igt@gem_exec_suspend@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/bat-rpls-2/igt@gem_exec_suspend@[email protected]
* igt@i915_selftest@live@guc:
- {bat-rpls-2}: [DMESG-WARN][49] ([i915#6471]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/bat-rpls-2/igt@i915_selftest@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/bat-rpls-2/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@hangcheck:
- {bat-adlm-1}: [INCOMPLETE][51] ([i915#4983]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/bat-adlm-1/igt@i915_selftest@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/bat-adlm-1/igt@i915_selftest@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor@atomic-transitions:
- fi-bsw-kefka: [FAIL][53] ([i915#6298]) -> [PASS][54]
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12418/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/fi-bsw-kefka/igt@kms_cursor_legacy@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[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#1759]: https://gitlab.freedesktop.org/drm/intel/issues/1759
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[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#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5278]: https://gitlab.freedesktop.org/drm/intel/issues/5278
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5591]: https://gitlab.freedesktop.org/drm/intel/issues/5591
[i915#6298]: https://gitlab.freedesktop.org/drm/intel/issues/6298
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6471]: https://gitlab.freedesktop.org/drm/intel/issues/6471
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7073]: https://gitlab.freedesktop.org/drm/intel/issues/7073
[i915#7346]: https://gitlab.freedesktop.org/drm/intel/issues/7346
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
Build changes
-------------
* Linux: CI_DRM_12418 -> Patchwork_111220v1
CI-20190529: 20190529
CI_DRM_12418: 22789b788bcaf35826550836b0ad6872d6e85ca6 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7071: 0801475083ccb938b1d3b358502ff97fdb435585 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111220v1: 22789b788bcaf35826550836b0ad6872d6e85ca6 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
9e9e95148c73 drm/i915/mtl: Add hardware-level lock for steering defcae9e5536 drm/i915/gt: Add dedicated MCR lock30574719744f drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes 41b1ea269875 drm/i915/gt: Correct kerneldoc for intel_gt_mcr_wait_for_reg()
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v1/index.html