i915: dedicated MCR locking and hardware semaphore
Subsystems (2)
v2 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.
v2:
- Use irqsave/irqrestore locking; on platforms that use execlist submission instead of GuC, MCR accesses can happen in interrupt context (tasklet) during reset -> error dump.
- Extend timeout for hardware semaphore and CI taint if we ever encounter it (this implies a hardware/firmware problem). (Mika)
- Add an extra patch optimizing xehp_setup_private_ppat by holding forcewake & mcr lock over the sequence of register writes. (Bala)
Matt Roper (5):
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 drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
drivers/gpu/drm/i915/gt/intel_gt.c | 7 +- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 129 ++++++++++++++++++-- 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_gtt.c | 27 ++-- drivers/gpu/drm/i915/gt/intel_mocs.c | 3 + drivers/gpu/drm/i915/gt/intel_workarounds.c | 12 +- 8 files changed, 162 insertions(+), 27 deletions(-)
Signature · 1 line
2.38.1
PATCH v2 1/5 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
Re: [PATCH v2 1/5] drm/i915/gt: Correct kerneldoc for intel_gt_mcr_wait_for_reg()
Quoted 6 lines · Matt Roper
The kerneldoc function name was not updated when this function was converted to a non-fw form.
Fixes 192bb40f030a ("drm/i915/gt: Manage uncore->lock while waiting on MCR register")Reported-by kernel test robot <[email protected]>Signed-off-by Matt Roper <[email protected]>
Regards,
Bala
Quoted 20 lines
--- 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 v2 2/5 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 following 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
Re: [PATCH v2 2/5] drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes
Quoted 5 lines · Matt Roper
Passing 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 following patch.
Signed-off-by Matt Roper <[email protected]>
Regards,
Bala
Quoted 92 lines
--- 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 v2 3/5 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.
v2:
- Use irqsave/irqrestore spinlock calls; platforms using execlist submission rather than GuC submission can perform MCR accesses in interrupt context because reset -> errordump happens in a tasklet.
--- drivers/gpu/drm/i915/gt/intel_gt.c | 7 +- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 79 +++++++++++++++++++-- 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 | 3 + drivers/gpu/drm/i915/gt/intel_workarounds.c | 12 ++-- 6 files changed, 101 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/gt/intel_gt.c +5 -2
@@ -1079,6 +1079,7 @@ static void mmio_invalidate_full(struct intel_gt *gt)enum intel_engine_id id;const i915_reg_t *regs;unsigned int num =0 ; +unsigned long flags;if (GRAPHICS_VER_FULL (i915) >=IP_VER (12 ,50 )) { regs =NULL ;
@@ -1099,7 +1100,8 @@ static void mmio_invalidate_full(struct intel_gt *gt)intel_uncore_forcewake_get (uncore,FORCEWAKE_ALL ); -spin_lock_irq (&uncore->lock);/* serialise invalidate with GT reset */ +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);/* serialise invalidate with GT reset */ awake =0 ;for_each_engine (engine, gt, id) {
@@ -1133,7 +1135,8 @@ static void mmio_invalidate_full(struct intel_gt *gt) IS_ALDERLAKE_P(i915)))intel_uncore_write_fw (uncore,GEN12_OA_TLB_INV_CR ,1 ); -spin_unlock_irq (&uncore->lock); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags);for_each_engine_masked (engine, gt, awake, tmp) {struct reg_and_bit rb;
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +75 -4
191 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,unsigned long *flags); +void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags); 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 +3 -0
@@ -613,14 +613,17 @@ static u32 l3cc_combine(u16 low, u16 high)static void init_l3cc_table (struct intel_gt *gt,const struct drm_i915_mocs_table *table) { +unsigned long flags;unsigned int i;u32 l3cc; +intel_gt_mcr_lock (gt, &flags);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, flags); }void intel_mocs_init_engine (struct intel_engine_cs *engine)
drivers/gpu/drm/i915/gt/intel_workarounds.c +8 -4
@@ -1760,7 +1760,8 @@ static void wa_list_apply(const struct i915_wa_list *wal) fw =wal_get_fw_for_rmw (uncore, wal); -spin_lock_irqsave (&uncore->lock, flags); +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);intel_uncore_forcewake_get__locked (uncore, fw);for (i =0 , wa = wal->list; i < wal->count; i++, wa++) {
@@ -1789,7 +1790,8 @@ static void wa_list_apply(const struct i915_wa_list *wal) }intel_uncore_forcewake_put__locked (uncore, fw); -spin_unlock_irqrestore (&uncore->lock, flags); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags); }void intel_gt_apply_workarounds (struct intel_gt *gt)
@@ -1810,7 +1812,8 @@ static bool wa_list_verify(struct intel_gt *gt, fw =wal_get_fw_for_rmw (uncore, wal); -spin_lock_irqsave (&uncore->lock, flags); +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);intel_uncore_forcewake_get__locked (uncore, fw);for (i =0 , wa = wal->list; i < wal->count; i++, wa++)
@@ -1820,7 +1823,8 @@ static bool wa_list_verify(struct intel_gt *gt, wal->name, from);intel_uncore_forcewake_put__locked (uncore, fw); -spin_unlock_irqrestore (&uncore->lock, flags); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags);return ok; }
Signature · 1 line
2.38.1
Re: [PATCH v2 3/5] drm/i915/gt: Add dedicated MCR lock
Quoted 19 lines · Matt Roper
We've been overloading
uncore->lockto protect access to the MCR steering register. That's not really whatuncore->lockis 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-trafficuncore->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.
v2:
- Use irqsave/irqrestore spinlock calls; platforms using execlist submission rather than GuC submission can perform MCR accesses in interrupt context because reset -> errordump happens in a tasklet.
Quoted 4 lines
Cc Chris Wilson <[email protected]>Cc Mika Kuoppala <[email protected]>Cc Balasubramani Vivekanandan <[email protected]>Signed-off-by Matt Roper <[email protected]>
Regards,
Bala
Quoted 353 lines
--- drivers/gpu/drm/i915/gt/intel_gt.c | 7 +- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 79 +++++++++++++++++++-- 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 | 3 + drivers/gpu/drm/i915/gt/intel_workarounds.c | 12 ++-- 6 files changed, 101 insertions(+), 10 deletions(-)drivers/gpu/drm/i915/gt/intel_gt.c +5
-2@@ -1079,6 +1079,7 @@ static void mmio_invalidate_full(struct intel_gt *gt)enum intel_engine_id id;const i915_reg_t *regs;unsigned int num =0 ; +unsigned long flags;if (GRAPHICS_VER_FULL (i915) >=IP_VER (12 ,50 )) { regs =NULL ;@@ -1099,7 +1100,8 @@ static void mmio_invalidate_full(struct intel_gt *gt)intel_uncore_forcewake_get (uncore,FORCEWAKE_ALL ); -spin_lock_irq (&uncore->lock);/* serialise invalidate with GT reset */ +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);/* serialise invalidate with GT reset */ awake =0 ;for_each_engine (engine, gt, id) {@@ -1133,7 +1135,8 @@ static void mmio_invalidate_full(struct intel_gt *gt) IS_ALDERLAKE_P(i915)))intel_uncore_write_fw (uncore,GEN12_OA_TLB_INV_CR ,1 ); -spin_unlock_irq (&uncore->lock); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags);for_each_engine_masked (engine, gt, awake, tmp) {struct reg_and_bit rb;drivers/gpu/drm/i915/gt/intel_gt_mcr.c +75
-4@@ -143,6 +143,8 @@ void intel_gt_mcr_init(struct intel_gt *gt)unsigned long fuse;int i; +spin_lock_init (>->mcr_lock); +/* * An mslice is unavailable only if both the meml3 for the slice is * disabled *and* all of the DSS in the slice (quadrant) are disabled. @@ -228,6 +230,7 @@ static i915_reg_t mcr_reg_cast(const i915_mcr_reg_t mcr)* @instance: instance number (documented as "subsliceid" on older platforms) * @value: register value to be written (ignored for read) * +* Context: The caller must hold the MCR lock * Return: 0 for write access. register value for read access. * * Caller needs to make sure the relevant forcewake wells are up. @@ -239,7 +242,7 @@ static u32 rw_with_mcr_steering_fw(struct intel_gt *gt,struct intel_uncore *uncore = gt->uncore;u32 mcr_mask, mcr_ss, mcr, old_mcr, val =0 ; -lockdep_assert_held (&uncore->lock); +lockdep_assert_held (>->mcr_lock);if (GRAPHICS_VER_FULL (uncore->i915) >=IP_VER (12 ,70 )) {/* @@ -316,6 +319,7 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt, {struct intel_uncore *uncore = gt->uncore;enum forcewake_domains fw_domains; +unsigned long flags;u32 val; fw_domains = intel_uncore_forcewake_for_reg(uncore, mcr_reg_cast(reg),@@ -324,17 +328,59 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,GEN8_MCR_SELECTOR , FW_REG_READ | FW_REG_WRITE); -spin_lock_irq (&uncore->lock); +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);intel_uncore_forcewake_get__locked (uncore, fw_domains); 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); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags);return val; } +/** +* intel_gt_mcr_lock - Acquire MCR steering lock +* @gt: GT structure +* @flags: storage to save IRQ flags to +* +* 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). +* +* Context: Takes gt->mcr_lock. uncore->lock should *not* be held when this +* function is called, although it may be acquired after this +* function call. +*/ +void intel_gt_mcr_lock (struct intel_gt *gt,unsigned long *flags) +{ +unsigned long __flags; + +lockdep_assert_not_held (>->uncore->lock); + +spin_lock_irqsave (>->mcr_lock, __flags); + + *flags = __flags; +} + +/** +* intel_gt_mcr_unlock - Release MCR steering lock +* @gt: GT structure +* @flags: IRQ flags to restore +* +* Releases the lock acquired by intel_gt_mcr_lock(). +* +* Context: Releases gt->mcr_lock +*/ +void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags) +{ +spin_unlock_irqrestore (>->mcr_lock, flags); +} +/** * intel_gt_mcr_read - read a specific instance of an MCR register * @gt: GT structure @@ -342,6 +388,8 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @group: the MCR group * @instance: the MCR instance * +* Context: Takes and releases gt->mcr_lock +* * Returns the value read from an MCR register after steering toward a specific * group/instance. */ @@ -362,6 +410,8 @@ u32 intel_gt_mcr_read(struct intel_gt *gt,* * Write an MCR register in unicast mode after steering toward a specific * group/instance. +* +* Context: Calls a function that takes and releases gt->mcr_lock */ void intel_gt_mcr_unicast_write (struct intel_gt *gt,i915_mcr_reg_t reg,u32 value,int group,int instance)@@ -376,10 +426,16 @@ void intel_gt_mcr_unicast_write(struct intel_gt *gt, i915_mcr_reg_t reg, u32 val* @value: value to write * * Write an MCR register in multicast mode to update all instances. +* +* Context: Takes and releases gt->mcr_lock */ void intel_gt_mcr_multicast_write (struct intel_gt *gt,i915_mcr_reg_t reg,u32 value) { +unsigned long flags; + +intel_gt_mcr_lock (gt, &flags); +/* * Ensure we have multicast behavior, just in case some non-i915 agent * left the hardware in unicast mode. @@ -388,6 +444,8 @@ void intel_gt_mcr_multicast_write(struct intel_gt *gt,intel_uncore_write_fw (gt->uncore,MTL_MCR_SELECTOR ,GEN11_MCR_MULTICAST );intel_uncore_write (gt->uncore,mcr_reg_cast (reg), value); + +intel_gt_mcr_unlock (gt, flags); }/** @@ -400,9 +458,13 @@ void intel_gt_mcr_multicast_write(struct intel_gt *gt,* function assumes the caller is already holding any necessary forcewake * domains; use intel_gt_mcr_multicast_write() in cases where forcewake should * be obtained automatically. +* +* Context: The caller must hold gt->mcr_lock. */ void intel_gt_mcr_multicast_write_fw (struct intel_gt *gt,i915_mcr_reg_t reg,u32 value) { +lockdep_assert_held (>->mcr_lock); +/* * Ensure we have multicast behavior, just in case some non-i915 agent * left the hardware in unicast mode. @@ -429,6 +491,8 @@ void intel_gt_mcr_multicast_write_fw(struct intel_gt *gt, i915_mcr_reg_t reg, u3* domains; use intel_gt_mcr_multicast_rmw() in cases where forcewake should * be obtained automatically. * +* Context: Calls functions that take and release gt->mcr_lock +* * Returns the old (unmodified) value read. */ u32 intel_gt_mcr_multicast_rmw(struct intel_gt *gt, i915_mcr_reg_t reg,@@ -580,6 +644,8 @@ void intel_gt_mcr_get_nonterminated_steering(struct intel_gt *gt,* domains; use intel_gt_mcr_read_any() in cases where forcewake should be * obtained automatically. * +* Context: The caller must hold gt->mcr_lock. +* * Returns the value from a non-terminated instance of @reg. */ u32 intel_gt_mcr_read_any_fw (struct intel_gt *gt,i915_mcr_reg_t reg)@@ -587,6 +653,8 @@ u32 intel_gt_mcr_read_any_fw(struct intel_gt *gt, i915_mcr_reg_t reg)int type;u8 group, instance; +lockdep_assert_held (>->mcr_lock); +for (type =0 ; type <NUM_STEERING_TYPES ; type++) {if (reg_needs_read_steering (gt, reg, type)) {get_nonterminated_steering (gt, type, &group, &instance);@@ -607,6 +675,8 @@ u32 intel_gt_mcr_read_any_fw(struct intel_gt *gt, i915_mcr_reg_t reg)* Reads a GT MCR register. The read will be steered to a non-terminated * instance (i.e., one that isn't fused off or powered down by power gating). * +* Context: Calls a function that takes and releases gt->mcr_lock. +* * Returns the value from a non-terminated instance of @reg. */ u32 intel_gt_mcr_read_any (struct intel_gt *gt,i915_mcr_reg_t reg)@@ -730,6 +800,7 @@ void intel_gt_mcr_get_ss_steering(struct intel_gt *gt, unsigned int dss,* Note that this routine assumes the caller holds forcewake asserted, it is * not suitable for very long waits. * +* Context: Calls a function that takes and releases gt->mcr_lock * Return: 0 if the register matches the desired condition, or -ETIMEDOUT. */ int intel_gt_mcr_wait_for_reg(struct intel_gt *gt,@@ -741,7 +812,7 @@ int intel_gt_mcr_wait_for_reg(struct intel_gt *gt, {int ret; -lockdep_assert_not_held (>->uncore->lock); +lockdep_assert_not_held (>->mcr_lock);#define done ((intel_gt_mcr_read_any(gt, reg) & mask) == value)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,unsigned long *flags); +void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags); 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 +3
-0@@ -613,14 +613,17 @@ static u32 l3cc_combine(u16 low, u16 high)static void init_l3cc_table (struct intel_gt *gt,const struct drm_i915_mocs_table *table) { +unsigned long flags;unsigned int i;u32 l3cc; +intel_gt_mcr_lock (gt, &flags);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, flags); }void intel_mocs_init_engine (struct intel_engine_cs *engine)drivers/gpu/drm/i915/gt/intel_workarounds.c +8
-4@@ -1760,7 +1760,8 @@ static void wa_list_apply(const struct i915_wa_list *wal) fw =wal_get_fw_for_rmw (uncore, wal); -spin_lock_irqsave (&uncore->lock, flags); +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);intel_uncore_forcewake_get__locked (uncore, fw);for (i =0 , wa = wal->list; i < wal->count; i++, wa++) {@@ -1789,7 +1790,8 @@ static void wa_list_apply(const struct i915_wa_list *wal) }intel_uncore_forcewake_put__locked (uncore, fw); -spin_unlock_irqrestore (&uncore->lock, flags); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags); }void intel_gt_apply_workarounds (struct intel_gt *gt)@@ -1810,7 +1812,8 @@ static bool wa_list_verify(struct intel_gt *gt, fw =wal_get_fw_for_rmw (uncore, wal); -spin_lock_irqsave (&uncore->lock, flags); +intel_gt_mcr_lock (gt, &flags); +spin_lock (&uncore->lock);intel_uncore_forcewake_get__locked (uncore, fw);for (i =0 , wa = wal->list; i < wal->count; i++, wa++)@@ -1820,7 +1823,8 @@ static bool wa_list_verify(struct intel_gt *gt, wal->name, from);intel_uncore_forcewake_put__locked (uncore, fw); -spin_unlock_irqrestore (&uncore->lock, flags); +spin_unlock (&uncore->lock); +intel_gt_mcr_unlock (gt, flags);return ok; }Signature · 1 line
2.38.1
PATCH v2 4/5 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 MTL_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.
v2:
- Extend hardware semaphore timeout and add a taint for CI if it ever happens (this would imply misbehaving hardware/firmware). (Mika)
- Add "MTL_" prefix to new steering semaphore register. (Mika)
--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 38 ++++++++++++++++++++++--- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + 2 files changed, 35 insertions(+), 4 deletions(-)
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +34 -4
@@ -347,10 +347,9 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @flags: storage to save IRQ flags to * * 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
@@ -359,12 +358,40 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,void intel_gt_mcr_lock (struct intel_gt *gt,unsigned long *flags) {unsigned long __flags; +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, +MTL_STEER_SEMAPHORE ) ==0x1 ,100 ); + +/* +* 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_irqsave (>->mcr_lock, __flags); *flags = __flags; + +/* +* In theory we should never fail to acquire the HW semaphore; this +* would indicate some hardware/firmware is misbehaving and not +* releasing it properly. +*/ +if (err == -ETIMEDOUT ) { +drm_err_ratelimited (>->i915->drm, +"GT%u hardware MCR steering semaphore timed out" , + gt->info.id); +add_taint_for_CI (gt->i915,TAINT_WARN );/* CI is now unreliable */ + } }/**
@@ -379,6 +406,9 @@ void intel_gt_mcr_lock(struct intel_gt *gt, unsigned long *flags)void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags) {spin_unlock_irqrestore (>->mcr_lock, flags); + +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) +intel_uncore_write_fw (gt->uncore,MTL_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 MTL_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
Re: [Intel-gfx] [PATCH v2 4/5] drm/i915/mtl: Add hardware-level lock for steering
Quoted 13 lines · Matt Roper
Starting 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
MTL_STEER_SEMAPHOREregister. Reading the register acts as a 'trylock' operation; the read will return0x1if the lock is acquired or0x0if something else is already holding the lock; once acquired, writing0x1to 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.
Quoted 7 lines
v2:
- Extend hardware semaphore timeout and add a taint for CI if it ever happens (this would imply misbehaving hardware/firmware). (Mika)
- Add "MTL_" prefix to new steering semaphore register. (Mika)Cc Mika Kuoppala <[email protected]>Signed-off-by Matt Roper <[email protected]>
Regards,
Bala
Quoted 89 lines
--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 38 ++++++++++++++++++++++--- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + 2 files changed, 35 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/gt/intel_gt_mcr.c +34
-4@@ -347,10 +347,9 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @flags: storage to save IRQ flags to * * 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 @@ -359,12 +358,40 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,void intel_gt_mcr_lock (struct intel_gt *gt,unsigned long *flags) {unsigned long __flags; +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, +MTL_STEER_SEMAPHORE ) ==0x1 ,100 ); + +/* +* 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_irqsave (>->mcr_lock, __flags); *flags = __flags; + +/* +* In theory we should never fail to acquire the HW semaphore; this +* would indicate some hardware/firmware is misbehaving and not +* releasing it properly. +*/ +if (err == -ETIMEDOUT ) { +drm_err_ratelimited (>->i915->drm, +"GT%u hardware MCR steering semaphore timed out" , + gt->info.id); +add_taint_for_CI (gt->i915,TAINT_WARN );/* CI is now unreliable */ + } }/** @@ -379,6 +406,9 @@ void intel_gt_mcr_lock(struct intel_gt *gt, unsigned long *flags)void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags) {spin_unlock_irqrestore (>->mcr_lock, flags); + +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) +intel_uncore_write_fw (gt->uncore,MTL_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 MTL_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
Re: [Intel-gfx] [PATCH v2 4/5] drm/i915/mtl: Add hardware-level lock for steering
In reply to Matt RoperQuoted 50 lines · Matt Roper
Starting 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
MTL_STEER_SEMAPHOREregister. Reading the register acts as a 'trylock' operation; the read will return0x1if the lock is acquired or0x0if something else is already holding the lock; once acquired, writing0x1to 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.
v2:
- Extend hardware semaphore timeout and add a taint for CI if it ever happens (this would imply misbehaving hardware/firmware). (Mika)
- Add "MTL_" prefix to new steering semaphore register. (Mika)Cc Mika Kuoppala <[email protected]>Signed-off-by Matt Roper <[email protected]>--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 38 ++++++++++++++++++++++--- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + 2 files changed, 35 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/gt/intel_gt_mcr.c +4
-4@@ -347,10 +347,9 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @flags: storage to save IRQ flags to * * 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 @@ -359,12 +358,40 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,void intel_gt_mcr_lock (struct intel_gt *gt,unsigned long *flags) {unsigned long __flags; +int err =0 ;lockdep_assert_not_held (>->uncore->lock);
drivers/gpu/drm/i915/gt/intel_gt_mcr.c static u32 rw_with_mcr_steering(struct intel_gt *gt, · line 373
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +9
-0+/* +* 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, +MTL_STEER_SEMAPHORE ) ==0x1 ,100 ); +
If two i915 threads enter here what happens? (Given hw locking is done before the spinlock.)
Regards,
Tvrtko
Quoted 46 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +21
-0+/* +* 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_irqsave (>->mcr_lock, __flags); *flags = __flags; + +/* +* In theory we should never fail to acquire the HW semaphore; this +* would indicate some hardware/firmware is misbehaving and not +* releasing it properly. +*/ +if (err == -ETIMEDOUT ) { +drm_err_ratelimited (>->i915->drm, +"GT%u hardware MCR steering semaphore timed out" , + gt->info.id); +add_taint_for_CI (gt->i915,TAINT_WARN );/* CI is now unreliable */ + } }/** @@ -379,6 +406,9 @@ void intel_gt_mcr_lock(struct intel_gt *gt, unsigned long *flags)void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags) {spin_unlock_irqrestore (>->mcr_lock, flags); + +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) +intel_uncore_write_fw (gt->uncore,MTL_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 MTL_STEER_SEMAPHORE _MMIO(0xfd0)#define MTL_MCR_SELECTOR _MMIO(0xfd4)#define SF_MCR_SELECTOR _MMIO(0xfd8)#define GEN8_MCR_SELECTOR _MMIO(0xfdc)
Re: [Intel-gfx] [PATCH v2 4/5] drm/i915/mtl: Add hardware-level lock for steering
Quoted 55 lines · Tvrtko Ursulin
Quoted 53 lines · Matt Roper
Starting 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
MTL_STEER_SEMAPHOREregister. Reading the register acts as a 'trylock' operation; the read will return0x1if the lock is acquired or0x0if something else is already holding the lock; once acquired, writing0x1to 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.
v2:
- Extend hardware semaphore timeout and add a taint for CI if it ever happens (this would imply misbehaving hardware/firmware). (Mika)
- Add "MTL_" prefix to new steering semaphore register. (Mika)Cc Mika Kuoppala <[email protected]>Signed-off-by Matt Roper <[email protected]>--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 38 ++++++++++++++++++++++--- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + 2 files changed, 35 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/gt/intel_gt_mcr.c +8
-4@@ -347,10 +347,9 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @flags: storage to save IRQ flags to * * 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 @@ -359,12 +358,40 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,void intel_gt_mcr_lock (struct intel_gt *gt,unsigned long *flags) {unsigned long __flags; +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.
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c static u32 rw_with_mcr_steering(struct intel_gt *gt, · line 373
Quoted 5 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +5
-0+*/ +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) + err =wait_for (intel_uncore_read_fw (gt->uncore, +MTL_STEER_SEMAPHORE ) ==0x1 ,100 ); +If two i915 threads enter here what happens? (Given hw locking is done before the spinlock.)
The second thread will see a '0' when it reads the register, indicating that something else (sw, fw, or hw) already has it locked. As soon as the first thread drops the lock, the next read will return '1' and allow the second thread to proceed.
Matt
Quoted 47 lines
Regards,
Tvrtko
Quoted 42 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +21
-0+/* +* 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_irqsave (>->mcr_lock, __flags); *flags = __flags; + +/* +* In theory we should never fail to acquire the HW semaphore; this +* would indicate some hardware/firmware is misbehaving and not +* releasing it properly. +*/ +if (err == -ETIMEDOUT ) { +drm_err_ratelimited (>->i915->drm, +"GT%u hardware MCR steering semaphore timed out" , + gt->info.id); +add_taint_for_CI (gt->i915,TAINT_WARN );/* CI is now unreliable */ + } }/** @@ -379,6 +406,9 @@ void intel_gt_mcr_lock(struct intel_gt *gt, unsigned long *flags)void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags) {spin_unlock_irqrestore (>->mcr_lock, flags); + +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) +intel_uncore_write_fw (gt->uncore,MTL_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 MTL_STEER_SEMAPHORE _MMIO(0xfd0)#define MTL_MCR_SELECTOR _MMIO(0xfd4)#define SF_MCR_SELECTOR _MMIO(0xfd8)#define GEN8_MCR_SELECTOR _MMIO(0xfdc)
Signature · 4 lines
Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation
Re: [Intel-gfx] [PATCH v2 4/5] drm/i915/mtl: Add hardware-level lock for steering
Quoted 65 lines · Matt Roper
Quoted 55 lines · Tvrtko Ursulin
Quoted 53 lines · Matt Roper
Starting 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
MTL_STEER_SEMAPHOREregister. Reading the register acts as a 'trylock' operation; the read will return0x1if the lock is acquired or0x0if something else is already holding the lock; once acquired, writing0x1to 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.
v2:
- Extend hardware semaphore timeout and add a taint for CI if it ever happens (this would imply misbehaving hardware/firmware). (Mika)
- Add "MTL_" prefix to new steering semaphore register. (Mika)Cc Mika Kuoppala <[email protected]>Signed-off-by Matt Roper <[email protected]>--- drivers/gpu/drm/i915/gt/intel_gt_mcr.c | 38 ++++++++++++++++++++++--- drivers/gpu/drm/i915/gt/intel_gt_regs.h | 1 + 2 files changed, 35 insertions(+), 4 deletions(-)drivers/gpu/drm/i915/gt/intel_gt_mcr.c +8
-4@@ -347,10 +347,9 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,* @flags: storage to save IRQ flags to * * 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 @@ -359,12 +358,40 @@ static u32 rw_with_mcr_steering(struct intel_gt *gt,void intel_gt_mcr_lock (struct intel_gt *gt,unsigned long *flags) {unsigned long __flags; +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. Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c static u32 rw_with_mcr_steering(struct intel_gt *gt, · line 373
Quoted 5 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +5
-0+*/ +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) + err =wait_for (intel_uncore_read_fw (gt->uncore, +MTL_STEER_SEMAPHORE ) ==0x1 ,100 ); +If two i915 threads enter here what happens? (Given hw locking is done before the spinlock.)
Quoted 4 lines
The second thread will see a '0' when it reads the register, indicating that something else (sw, fw, or hw) already has it locked. As soon as the first thread drops the lock, the next read will return '1' and allow the second thread to proceed.
I was worried if there was a concept of request originator, but this then sounds good.
Regards,
Tvrtko
Quoted 43 lines
Quoted 42 lines
Quoted 42 lines
drivers/gpu/drm/i915/gt/intel_gt_mcr.c +21
-0+/* +* 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_irqsave (>->mcr_lock, __flags); *flags = __flags; + +/* +* In theory we should never fail to acquire the HW semaphore; this +* would indicate some hardware/firmware is misbehaving and not +* releasing it properly. +*/ +if (err == -ETIMEDOUT ) { +drm_err_ratelimited (>->i915->drm, +"GT%u hardware MCR steering semaphore timed out" , + gt->info.id); +add_taint_for_CI (gt->i915,TAINT_WARN );/* CI is now unreliable */ + } }/** @@ -379,6 +406,9 @@ void intel_gt_mcr_lock(struct intel_gt *gt, unsigned long *flags)void intel_gt_mcr_unlock (struct intel_gt *gt,unsigned long flags) {spin_unlock_irqrestore (>->mcr_lock, flags); + +if (GRAPHICS_VER (gt->i915) >=IP_VER (12 ,70 )) +intel_uncore_write_fw (gt->uncore,MTL_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 MTL_STEER_SEMAPHORE _MMIO(0xfd0)#define MTL_MCR_SELECTOR _MMIO(0xfd4)#define SF_MCR_SELECTOR _MMIO(0xfd8)#define GEN8_MCR_SELECTOR _MMIO(0xfdc)
PATCH v2 5/5 drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
In reply to Matt RoperPPAT setup involves a series of multicast writes. This can be optimized slightly be acquiring forcewake and the steering lock just once for the entire sequence.
--- drivers/gpu/drm/i915/gt/intel_gtt.c | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-)
drivers/gpu/drm/i915/gt/intel_gtt.c +19 -8
@@ -482,14 +482,25 @@ static void tgl_setup_private_ppat(struct intel_uncore *uncore)static void xehp_setup_private_ppat (struct intel_gt *gt) { -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +enum forcewake_domains fw; +unsigned long flags; + + fw =intel_uncore_forcewake_for_reg (gt->uncore,_MMIO (XEHP_PAT_INDEX (0 ).reg), +FW_REG_READ ); +intel_uncore_forcewake_get (gt->uncore, fw); + +intel_gt_mcr_lock (gt, &flags); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +intel_gt_mcr_unlock (gt, flags); + +intel_uncore_forcewake_put (gt->uncore, fw); }static void icl_setup_private_ppat (struct intel_uncore *uncore)
Signature · 1 line
2.38.1
Re: [PATCH v2 5/5] drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
Quoted 21 lines · Matt Roper
PPAT setup involves a series of multicast writes. This can be optimized slightly be acquiring forcewake and the steering lock just once for the entire sequence.
Suggested-by Balasubramani Vivekanandan <[email protected]>Signed-off-by Matt Roper <[email protected]>--- drivers/gpu/drm/i915/gt/intel_gtt.c | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-)drivers/gpu/drm/i915/gt/intel_gtt.c +0
-3@@ -482,14 +482,25 @@ static void tgl_setup_private_ppat(struct intel_uncore *uncore)static void xehp_setup_private_ppat (struct intel_gt *gt) { -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT );
drivers/gpu/drm/i915/gt/intel_gtt.c static void tgl_setup_private_ppat(struct intel_uncore *uncore) · line 489
Quoted 10 lines
drivers/gpu/drm/i915/gt/intel_gtt.c +5
-5-intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +enum forcewake_domains fw; +unsigned long flags; + + fw =intel_uncore_forcewake_for_reg (gt->uncore,_MMIO (XEHP_PAT_INDEX (0 ).reg), +FW_REG_READ );
I am not completely aware of forcewake implementation. I am wondering if the last parameter should be FW_REG_WRITE since it is register write which is happening later.
Regards,
Bala
Quoted 20 lines
drivers/gpu/drm/i915/gt/intel_gtt.c +14
-0+intel_uncore_forcewake_get (gt->uncore, fw); + +intel_gt_mcr_lock (gt, &flags); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +intel_gt_mcr_unlock (gt, flags); + +intel_uncore_forcewake_put (gt->uncore, fw); }static void icl_setup_private_ppat (struct intel_uncore *uncore)Signature · 1 line
2.38.1
PATCH v3 5/5 drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
PPAT setup involves a series of multicast writes. This can be optimized slightly be acquiring forcewake and the steering lock just once for the entire sequence.
v2:
- We should use FW_REG_WRITE instead of FW_REG_READ. (Bala)
--- drivers/gpu/drm/i915/gt/intel_gtt.c | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-)
drivers/gpu/drm/i915/gt/intel_gtt.c +19 -8
@@ -482,14 +482,25 @@ static void tgl_setup_private_ppat(struct intel_uncore *uncore)static void xehp_setup_private_ppat (struct intel_gt *gt) { -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +enum forcewake_domains fw; +unsigned long flags; + + fw =intel_uncore_forcewake_for_reg (gt->uncore,_MMIO (XEHP_PAT_INDEX (0 ).reg), +FW_REG_WRITE ); +intel_uncore_forcewake_get (gt->uncore, fw); + +intel_gt_mcr_lock (gt, &flags); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +intel_gt_mcr_unlock (gt, flags); + +intel_uncore_forcewake_put (gt->uncore, fw); }static void icl_setup_private_ppat (struct intel_uncore *uncore)
Signature · 1 line
2.38.1
Re: [PATCH v3 5/5] drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
Quoted 9 lines · Matt Roper
PPAT setup involves a series of multicast writes. This can be optimized slightly be acquiring forcewake and the steering lock just once for the entire sequence.
v2:
- We should useFW_REG_WRITEinstead ofFW_REG_READ. (Bala)Suggested-by Balasubramani Vivekanandan <[email protected]>Signed-off-by Matt Roper <[email protected]>
Regards,
Bala
Quoted 45 lines
--- drivers/gpu/drm/i915/gt/intel_gtt.c | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-)drivers/gpu/drm/i915/gt/intel_gtt.c +19
-8@@ -482,14 +482,25 @@ static void tgl_setup_private_ppat(struct intel_uncore *uncore)static void xehp_setup_private_ppat (struct intel_gt *gt) { -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +enum forcewake_domains fw; +unsigned long flags; + + fw =intel_uncore_forcewake_for_reg (gt->uncore,_MMIO (XEHP_PAT_INDEX (0 ).reg), +FW_REG_WRITE ); +intel_uncore_forcewake_get (gt->uncore, fw); + +intel_gt_mcr_lock (gt, &flags); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +intel_gt_mcr_unlock (gt, flags); + +intel_uncore_forcewake_put (gt->uncore, fw); }static void icl_setup_private_ppat (struct intel_uncore *uncore)Signature · 1 line
2.38.1
Re: [PATCH v3 5/5] drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
Quoted 5 lines · Balasubramani Vivekanandan
Quoted 4 lines · Matt Roper
PPAT setup involves a series of multicast writes. This can be optimized slightly be acquiring forcewake and the steering lock just once for the entire sequence.
Quoted 7 lines
Quoted 5 lines
v2:
- We should useFW_REG_WRITEinstead ofFW_REG_READ. (Bala)Suggested-by Balasubramani Vivekanandan <[email protected]>Signed-off-by Matt Roper <[email protected]>Reviewed-by Balasubramani Vivekanandan <[email protected]>
Thanks. Since this patch is independent of patch #4 (the only one that hasn't been reviewed yet), I went ahead and pushed this one to drm-intel-gt-next. BTW, I noticed I wrote "mtl" in the patch title where I actually meant to have "mcr" (this isn't a MTL-specific change), so I corrected that typo while pushing as well.
Matt
Quoted 49 lines
Regards,
BalaQuoted 45 lines
--- drivers/gpu/drm/i915/gt/intel_gtt.c | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-)drivers/gpu/drm/i915/gt/intel_gtt.c +19
-8@@ -482,14 +482,25 @@ static void tgl_setup_private_ppat(struct intel_uncore *uncore)static void xehp_setup_private_ppat (struct intel_gt *gt) { -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +enum forcewake_domains fw; +unsigned long flags; + + fw =intel_uncore_forcewake_for_reg (gt->uncore,_MMIO (XEHP_PAT_INDEX (0 ).reg), +FW_REG_WRITE ); +intel_uncore_forcewake_get (gt->uncore, fw); + +intel_gt_mcr_lock (gt, &flags); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +intel_gt_mcr_unlock (gt, flags); + +intel_uncore_forcewake_put (gt->uncore, fw); }static void icl_setup_private_ppat (struct intel_uncore *uncore)Signature · 1 line
2.38.1
Signature · 4 lines
Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation
Re: [PATCH v2 5/5] drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup
In reply to Balasubramani VivekanandanQuoted 28 lines · Balasubramani Vivekanandan
Quoted 27 lines · Matt Roper
PPAT setup involves a series of multicast writes. This can be optimized slightly be acquiring forcewake and the steering lock just once for the entire sequence.
Suggested-by Balasubramani Vivekanandan <[email protected]>Signed-off-by Matt Roper <[email protected]>--- drivers/gpu/drm/i915/gt/intel_gtt.c | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-)drivers/gpu/drm/i915/gt/intel_gtt.c +1
-8@@ -482,14 +482,25 @@ static void tgl_setup_private_ppat(struct intel_uncore *uncore)static void xehp_setup_private_ppat (struct intel_gt *gt) { -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); -intel_gt_mcr_multicast_write (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +enum forcewake_domains fw;
Quoted 8 lines
drivers/gpu/drm/i915/gt/intel_gtt.c static void tgl_setup_private_ppat(struct intel_uncore *uncore) · line 489
Quoted 4 lines
drivers/gpu/drm/i915/gt/intel_gtt.c +4
-0+unsigned long flags; + + fw =intel_uncore_forcewake_for_reg (gt->uncore,_MMIO (XEHP_PAT_INDEX (0 ).reg), +FW_REG_READ );I am not completely aware of forcewake implementation. I am wondering if the last parameter should be
FW_REG_WRITEsince it is register write which is happening later.
Yep, good catch. Using FW_REG_WRITE allows the driver to potentially skip obtaining forcewake and waking the hardware if the registers being written are "shadowed" so it's always good to use FW_REG_WRITE in places where we're only writing and not reading.
In this case the specific registers in question don't appear to be part of the shadow table for any affected platforms (e.g., dg2_shadowed_regs[] and such in intel_uncore.c), so FW_REG_WRITE will still behave the same as FW_REG_READ here. But it's always possible that future platforms could decide to shadow these registers, so it's good to fix anyway; I just sent an updated copy of this patch making that change.
Matt
Quoted 24 lines
Regards,
BalaQuoted 20 lines
drivers/gpu/drm/i915/gt/intel_gtt.c +14
-0+intel_uncore_forcewake_get (gt->uncore, fw); + +intel_gt_mcr_lock (gt, &flags); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (0 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (1 ),GEN8_PPAT_WC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (2 ),GEN8_PPAT_WT ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (3 ),GEN8_PPAT_UC ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (4 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (5 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (6 ),GEN8_PPAT_WB ); +intel_gt_mcr_multicast_write_fw (gt,XEHP_PAT_INDEX (7 ),GEN8_PPAT_WB ); +intel_gt_mcr_unlock (gt, flags); + +intel_uncore_forcewake_put (gt->uncore, fw); }static void icl_setup_private_ppat (struct intel_uncore *uncore)Signature · 1 line
2.38.1
Signature · 4 lines
Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for i915: dedicated MCR locking and hardware semaphore (rev2)
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev2)
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: success for i915: dedicated MCR locking and hardware semaphore (rev2)
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev2)
URL : https://patchwork.freedesktop.org/series/111220/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12440 -> Patchwork_111220v2
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/index.html
Participating hosts (34 -> 35)
------------------------------
Additional (1): bat-dg1-5
Known issues
------------
Here are the changes found in Patchwork_111220v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_mmap@basic:
- bat-dg1-5: NOTRUN -> [SKIP][1] ([i915#4083])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@gem_tiled_fence_blits@basic:
- bat-dg1-5: NOTRUN -> [SKIP][2] ([i915#4077]) +2 similar issues
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@gem_tiled_pread_basic:
- bat-dg1-5: NOTRUN -> [SKIP][3] ([i915#4079]) +1 similar issue
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@gem_tiled_pread_basic.html
* igt@i915_pm_backlight@basic-brightness:
- bat-dg1-5: NOTRUN -> [SKIP][4] ([i915#7561])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@i915_pm_rps@basic-api:
- bat-dg1-5: NOTRUN -> [SKIP][5] ([i915#6621])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@kms_addfb_basic@basic-x-tiled-legacy:
- bat-dg1-5: NOTRUN -> [SKIP][6] ([i915#4212]) +7 similar issues
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@kms_addfb_basic@basic-y-tiled-legacy:
- bat-dg1-5: NOTRUN -> [SKIP][7] ([i915#4215])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- bat-dg1-5: NOTRUN -> [SKIP][8] ([fdo#111827]) +8 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- bat-dg1-5: NOTRUN -> [SKIP][9] ([i915#4103] / [i915#4213])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@kms_force_connector_basic@force-load-detect:
- bat-dg1-5: NOTRUN -> [SKIP][10] ([fdo#109285])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@kms_psr@sprite_plane_onoff:
- bat-dg1-5: NOTRUN -> [SKIP][11] ([i915#1072] / [i915#4078]) +3 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@kms_psr@sprite_plane_onoff.html
* igt@kms_setmode@basic-clone-single-crtc:
- bat-dg1-5: NOTRUN -> [SKIP][12] ([i915#3555])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@prime_vgem@basic-fence-read:
- bat-dg1-5: NOTRUN -> [SKIP][13] ([i915#3708]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@prime_vgem@basic-gtt:
- bat-dg1-5: NOTRUN -> [SKIP][14] ([i915#3708] / [i915#4077]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
* igt@prime_vgem@basic-userptr:
- bat-dg1-5: NOTRUN -> [SKIP][15] ([i915#3708] / [i915#4873])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-dg1-5/igt@[email protected]
#### Possible fixes ####
* igt@gem_tiled_blits@basic:
- fi-pnv-d510: [SKIP][16] ([fdo#109271]) -> [PASS][17] +1 similar issue
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/fi-pnv-d510/igt@[email protected]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/fi-pnv-d510/igt@[email protected]
* igt@i915_module_load@reload:
- {bat-rpls-2}: [INCOMPLETE][18] ([i915#6434]) -> [PASS][19]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/bat-rpls-2/igt@[email protected]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-rpls-2/igt@[email protected]
* igt@i915_selftest@live@reset:
- {bat-rpls-1}: [DMESG-FAIL][20] ([i915#4983]) -> [PASS][21]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/bat-rpls-1/igt@i915_selftest@[email protected]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/bat-rpls-1/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#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109285]: https://bugs.freedesktop.org/show_bug.cgi?id=109285
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4079]: https://gitlab.freedesktop.org/drm/intel/issues/4079
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4212]: https://gitlab.freedesktop.org/drm/intel/issues/4212
[i915#4213]: https://gitlab.freedesktop.org/drm/intel/issues/4213
[i915#4215]: https://gitlab.freedesktop.org/drm/intel/issues/4215
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#6257]: https://gitlab.freedesktop.org/drm/intel/issues/6257
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6621]: https://gitlab.freedesktop.org/drm/intel/issues/6621
[i915#7346]: https://gitlab.freedesktop.org/drm/intel/issues/7346
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
Build changes
-------------
* Linux: CI_DRM_12440 -> Patchwork_111220v2
CI-20190529: 20190529
CI_DRM_12440: d21d6474a37e5d43075a24668807ea40a7ee9fc1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7073: d021d66e389f4a759dc749b5f74f278ecd2e6cbf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111220v2: d21d6474a37e5d43075a24668807ea40a7ee9fc1 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
d71b0e61a00d drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup 42977cf2e213 drm/i915/mtl: Add hardware-level lock for steering 8a9918e52cb8 drm/i915/gt: Add dedicated MCR lockae2d20825a99 drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes 49c44b44ca4c 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_111220v2/index.html
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for i915: dedicated MCR locking and hardware semaphore (rev2)
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev2)
URL : https://patchwork.freedesktop.org/series/111220/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12440_full -> Patchwork_111220v2_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_111220v2_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_111220v2_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
Participating hosts (10 -> 10)
------------------------------
No changes in participating hosts
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_111220v2_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb3/igt@gem_ctx_isolation@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb8/igt@gem_ctx_isolation@[email protected]
Known issues
------------
Here are the changes found in Patchwork_111220v2_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@smoketest:
- shard-iclb: [PASS][3] -> [FAIL][4] ([i915#5099])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb5/igt@[email protected]
* igt@gem_exec_balancer@parallel:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#4525]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][7] ([i915#2842])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_params@secure-non-root:
- shard-iclb: NOTRUN -> [SKIP][8] ([fdo#112283])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#2190])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@[email protected]
* igt@gem_lmem_swapping@heavy-verify-random:
- shard-apl: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#4613])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@[email protected]
* igt@gem_lmem_swapping@parallel-random-verify:
- shard-skl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
* igt@gem_lmem_swapping@verify-random-ccs:
- shard-tglb: NOTRUN -> [SKIP][12] ([i915#4613])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]
* igt@gem_pxp@create-protected-buffer:
- shard-iclb: NOTRUN -> [SKIP][13] ([i915#4270])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@gem_render_copy@x-tiled-to-vebox-y-tiled:
- shard-iclb: NOTRUN -> [SKIP][14] ([i915#768])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@gem_userptr_blits@coherency-unsync:
- shard-iclb: NOTRUN -> [SKIP][15] ([i915#3297]) +2 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@gem_userptr_blits@input-checking:
- shard-skl: NOTRUN -> [DMESG-WARN][16] ([i915#4991])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@[email protected]
* igt@gen9_exec_parse@bb-start-far:
- shard-iclb: NOTRUN -> [SKIP][17] ([i915#2856])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@i915_pm_dc@dc6-dpms:
- shard-skl: NOTRUN -> [FAIL][18] ([i915#3989] / [i915#454])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@[email protected]
* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- shard-skl: [PASS][19] -> [WARN][20] ([i915#1804])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl9/igt@i915_pm_rc6_residency@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl6/igt@i915_pm_rc6_residency@[email protected]
* igt@i915_pm_rps@engine-order:
- shard-apl: NOTRUN -> [FAIL][21] ([i915#6537])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@[email protected]
* igt@i915_pm_sseu@full-enable:
- shard-skl: [PASS][22] -> [FAIL][23] ([i915#7084])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl3/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl3/igt@[email protected]
* igt@i915_selftest@mock@timelines:
- shard-tglb: NOTRUN -> [INCOMPLETE][24] ([i915#7605])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@i915_selftest@[email protected]
* igt@kms_async_flips@alternate-sync-async-flip@pipe-a-edp-1:
- shard-skl: [PASS][25] -> [FAIL][26] ([i915#2521])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl9/igt@kms_async_flips@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl6/igt@kms_async_flips@[email protected]
* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180:
- shard-iclb: NOTRUN -> [SKIP][27] ([i915#5286])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][28] ([fdo#109271] / [i915#3886]) +3 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][29] ([fdo#109278] / [i915#3886])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3886])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs.html
* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs:
- shard-iclb: NOTRUN -> [SKIP][31] ([fdo#109278]) +7 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs.html
* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_ccs:
- shard-apl: NOTRUN -> [SKIP][32] ([fdo#109271]) +60 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_ccs.html
* igt@kms_chamelium@dp-audio-edid:
- shard-tglb: NOTRUN -> [SKIP][33] ([fdo#109284] / [fdo#111827])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]
* igt@kms_chamelium@dp-hpd-for-each-pipe:
- shard-iclb: NOTRUN -> [SKIP][34] ([fdo#109284] / [fdo#111827]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@kms_chamelium@hdmi-hpd-for-each-pipe:
- shard-apl: NOTRUN -> [SKIP][35] ([fdo#109271] / [fdo#111827]) +4 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@[email protected]
* igt@kms_chamelium@hdmi-mode-timings:
- shard-skl: NOTRUN -> [SKIP][36] ([fdo#109271] / [fdo#111827]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
* igt@kms_content_protection@atomic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [TIMEOUT][37] ([i915#7173])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@kms_content_protection@[email protected]
* igt@kms_cursor_crc@cursor-rapid-movement-512x512:
- shard-tglb: NOTRUN -> [SKIP][38] ([i915#3359])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]
* igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic:
- shard-iclb: NOTRUN -> [SKIP][39] ([fdo#109274]) +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- shard-iclb: NOTRUN -> [SKIP][40] ([i915#4103])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-tglb: [PASS][41] -> [FAIL][42] ([i915#2346]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb6/igt@kms_cursor_legacy@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@kms_cursor_legacy@[email protected]
* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][43] -> [FAIL][44] ([i915#79]) +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@kms_flip@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl1/igt@kms_flip@[email protected]
* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1:
- shard-skl: [PASS][45] -> [FAIL][46] ([i915#2122]) +4 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@kms_flip@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl4/igt@kms_flip@[email protected]
* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][47] ([i915#2587] / [i915#2672]) +4 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb6/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode.html
* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][48] ([i915#2672] / [i915#3555])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][49] ([i915#3555]) +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode.html
* igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][50] ([i915#2672]) +4 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-upscaling@pipe-a-default-mode.html
* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-shrfb-pgflip-blt:
- shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109280]) +8 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-shrfb-pgflip-blt.html
* igt@kms_frontbuffer_tracking@fbcpsr-modesetfrombusy:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#6497]) +1 similar issue
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-skl: NOTRUN -> [SKIP][53] ([fdo#109271]) +40 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][54] ([i915#4573]) +2 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_plane_scaling@planes-upscale-factor-0-25@pipe-a-edp-1:
- shard-skl: [PASS][55] -> [DMESG-WARN][56] ([i915#1982])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl10/igt@kms_plane_scaling@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl3/igt@kms_plane_scaling@[email protected]
* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf:
- shard-apl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#658]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-skl: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#658]) +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: NOTRUN -> [SKIP][59] ([fdo#109642] / [fdo#111068] / [i915#658]) +1 similar issue
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_psr2_su@page_flip-xrgb8888.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][60] -> [SKIP][61] ([fdo#109441])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_scaling_modes@scaling-mode-none@edp-1-pipe-b:
- shard-iclb: NOTRUN -> [SKIP][62] ([i915#5030]) +2 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_scaling_modes@[email protected]
* igt@perf@gen12-oa-tlb-invalidate:
- shard-iclb: NOTRUN -> [SKIP][63] ([fdo#109289])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@sysfs_clients@recycle:
- shard-iclb: NOTRUN -> [SKIP][64] ([i915#2994])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]
* igt@sysfs_clients@sema-10:
- shard-skl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#2994])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
* igt@sysfs_heartbeat_interval@mixed@vecs0:
- shard-skl: [PASS][66] -> [FAIL][67] ([i915#1731])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl4/igt@sysfs_heartbeat_interval@[email protected]
#### Possible fixes ####
* igt@drm_read@empty-block:
- {shard-rkl}: [SKIP][68] ([i915#1845] / [i915#4098]) -> [PASS][69] +7 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-2/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-6/igt@[email protected]
* igt@fbdev@unaligned-read:
- {shard-rkl}: [SKIP][70] ([i915#2582]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-2/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-6/igt@[email protected]
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-apl: [DMESG-WARN][72] ([i915#180]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl6/igt@gem_ctx_isolation@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@gem_ctx_isolation@[email protected]
* igt@gem_eio@in-flight-suspend:
- {shard-rkl}: [FAIL][74] ([fdo#103375]) -> [PASS][75]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]
* igt@gem_eio@reset-stress:
- {shard-dg1}: [FAIL][76] ([i915#5784]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-dg1-19/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-dg1-15/igt@[email protected]
* igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: [SKIP][78] ([i915#4525]) -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb6/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@[email protected]
* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [FAIL][80] ([i915#2842]) -> [PASS][81]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb7/igt@gem_exec_fair@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb5/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: [FAIL][82] ([i915#2842]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl8/igt@gem_exec_fair@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl3/igt@gem_exec_fair@[email protected]
* igt@gem_exec_fair@basic-pace@vcs0:
- shard-iclb: [FAIL][84] ([i915#2842]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@gem_exec_fair@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@gem_exec_fair@[email protected]
* igt@gem_exec_reloc@basic-wc-cpu:
- {shard-rkl}: [SKIP][86] ([i915#3281]) -> [PASS][87] +2 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]
* igt@gem_exec_whisper@basic-contexts-priority:
- {shard-rkl}: [FAIL][88] -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-5/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-3/igt@[email protected]
* igt@gem_readwrite@read-write:
- {shard-rkl}: [SKIP][90] ([i915#3282]) -> [PASS][91] +1 similar issue
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]
* igt@gen9_exec_parse@allowed-single:
- shard-apl: [DMESG-WARN][92] ([i915#5566] / [i915#716]) -> [PASS][93]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl2/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@[email protected]
* igt@gen9_exec_parse@bb-start-far:
- {shard-rkl}: [SKIP][94] ([i915#2527]) -> [PASS][95]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]
* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [SKIP][96] ([i915#4281]) -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb6/igt@[email protected]
* igt@i915_selftest@live@gt_heartbeat:
- shard-skl: [DMESG-FAIL][98] ([i915#5334]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl4/igt@i915_selftest@live@gt_heartbeat.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl7/igt@i915_selftest@live@gt_heartbeat.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-skl: [FAIL][100] ([i915#79]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@kms_flip@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@kms_flip@[email protected]
* igt@kms_flip@flip-vs-suspend@c-edp1:
- shard-tglb: [DMESG-WARN][102] ([i915#2411] / [i915#2867]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb8/igt@kms_flip@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-render:
- {shard-rkl}: [SKIP][104] ([i915#1849] / [i915#4098]) -> [PASS][105] +6 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-render.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-render.html
* igt@kms_psr@psr2_sprite_mmap_cpu:
- shard-iclb: [SKIP][106] ([fdo#109441]) -> [PASS][107] +1 similar issue
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@kms_psr@psr2_sprite_mmap_cpu.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_cpu.html
* igt@perf@polling:
- shard-skl: [FAIL][108] ([i915#1542]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl9/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl1/igt@[email protected]
#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][110] ([i915#658]) -> [SKIP][111] ([i915#588])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb6/igt@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@[email protected]
* igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1:
- shard-apl: [FAIL][112] ([i915#4573]) -> [DMESG-FAIL][113] ([IGT#6]) +1 similar issue
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl6/igt@kms_plane_alpha_blend@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl2/igt@kms_plane_alpha_blend@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-iclb: [SKIP][114] ([fdo#111068] / [i915#658]) -> [SKIP][115] ([i915#2920])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb6/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@[email protected]
* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][116] ([i915#2920]) -> [SKIP][117] ([fdo#111068] / [i915#658])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb2/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb6/igt@[email protected]
* igt@runner@aborted:
- shard-apl: ([FAIL][118], [FAIL][119], [FAIL][120], [FAIL][121]) ([fdo#109271] / [i915#180] / [i915#3002] / [i915#4312]) -> ([FAIL][122], [FAIL][123]) ([i915#3002] / [i915#4312])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl6/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl7/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl1/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl2/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl2/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl8/igt@[email protected]
- shard-skl: [FAIL][124] ([i915#6949]) -> ([FAIL][125], [FAIL][126], [FAIL][127]) ([i915#3002] / [i915#4312] / [i915#6949])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl1/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl3/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308
[fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111656]: https://bugs.freedesktop.org/show_bug.cgi?id=111656
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054
[fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722
[i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3938]: https://gitlab.freedesktop.org/drm/intel/issues/3938
[i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989
[i915#4036]: https://gitlab.freedesktop.org/drm/intel/issues/4036
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4171]: https://gitlab.freedesktop.org/drm/intel/issues/4171
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4881]: https://gitlab.freedesktop.org/drm/intel/issues/4881
[i915#4936]: https://gitlab.freedesktop.org/drm/intel/issues/4936
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5030]: https://gitlab.freedesktop.org/drm/intel/issues/5030
[i915#5099]: https://gitlab.freedesktop.org/drm/intel/issues/5099
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5461]: https://gitlab.freedesktop.org/drm/intel/issues/5461
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6227]: https://gitlab.freedesktop.org/drm/intel/issues/6227
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6334]: https://gitlab.freedesktop.org/drm/intel/issues/6334
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#6537]: https://gitlab.freedesktop.org/drm/intel/issues/6537
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6949]: https://gitlab.freedesktop.org/drm/intel/issues/6949
[i915#7084]: https://gitlab.freedesktop.org/drm/intel/issues/7084
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#7605]: https://gitlab.freedesktop.org/drm/intel/issues/7605
[i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
Build changes
-------------
* Linux: CI_DRM_12440 -> Patchwork_111220v2
CI-20190529: 20190529
CI_DRM_12440: d21d6474a37e5d43075a24668807ea40a7ee9fc1 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7073: d021d66e389f4a759dc749b5f74f278ecd2e6cbf @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111220v2: d21d6474a37e5d43075a24668807ea40a7ee9fc1 @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/index.html
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for i915: dedicated MCR locking and hardware semaphore (rev2)
Quoted 35 lines · Patchwork
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev2)
URL : https://patchwork.freedesktop.org/series/111220/
State : failure== Summary ==
CI Bug Log - changes from
CI_DRM_12440_full->Patchwork_111220v2_full
====================================================Summary
-------**FAILURE**
Serious unknown changes coming with
Patchwork_111220v2_fullabsolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_111220v2_full, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.Participating hosts (10 -> 10)
------------------------------No changes in participating hosts
Possible new issues
-------------------Here are the unknown changes that may have been introduced in
Patchwork_111220v2_full:
Quoted 8 lines
### IGT changes ###
#### Possible regressions ####
* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-tglb: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb3/igt@gem_ctx_isolation@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb8/igt@gem_ctx_isolation@[email protected]
System never came back from suspend. Not related to this series.
First three patches of the series applied to drm-intel-gt-next.
Matt
Quoted 525 lines
Known issues
------------Here are the changes found in
Patchwork_111220v2_fullthat come from known issues:### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@smoketest:
- shard-iclb: [PASS][3] -> [FAIL][4] ([i915#5099])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb5/igt@[email protected]* igt@gem_exec_balancer@parallel:
- shard-iclb: [PASS][5] -> [SKIP][6] ([i915#4525]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb2/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@gem_exec_fair@basic-pace@vcs1:
- shard-iclb: NOTRUN -> [FAIL][7] ([i915#2842])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@gem_exec_fair@[email protected]* igt@gem_exec_params@secure-non-root:
- shard-iclb: NOTRUN -> [SKIP][8] ([fdo#112283])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@gem_huc_copy@huc-copy:
- shard-apl: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#2190])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@[email protected]* igt@gem_lmem_swapping@heavy-verify-random:
- shard-apl: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#4613])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@[email protected]* igt@gem_lmem_swapping@parallel-random-verify:
- shard-skl: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]* igt@gem_lmem_swapping@verify-random-ccs:
- shard-tglb: NOTRUN -> [SKIP][12] ([i915#4613])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]* igt@gem_pxp@create-protected-buffer:
- shard-iclb: NOTRUN -> [SKIP][13] ([i915#4270])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@gem_render_copy@x-tiled-to-vebox-y-tiled:
- shard-iclb: NOTRUN -> [SKIP][14] ([i915#768])
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@gem_userptr_blits@coherency-unsync:
- shard-iclb: NOTRUN -> [SKIP][15] ([i915#3297]) +2 similar issues
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@gem_userptr_blits@input-checking:
- shard-skl: NOTRUN -> [DMESG-WARN][16] ([i915#4991])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@[email protected]* igt@gen9_exec_parse@bb-start-far:
- shard-iclb: NOTRUN -> [SKIP][17] ([i915#2856])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@i915_pm_dc@dc6-dpms:
- shard-skl: NOTRUN -> [FAIL][18] ([i915#3989] / [i915#454])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@[email protected]* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- shard-skl: [PASS][19] -> [WARN][20] ([i915#1804])
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl9/igt@i915_pm_rc6_residency@[email protected]
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl6/igt@i915_pm_rc6_residency@[email protected]* igt@i915_pm_rps@engine-order:
- shard-apl: NOTRUN -> [FAIL][21] ([i915#6537])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@[email protected]* igt@i915_pm_sseu@full-enable:
- shard-skl: [PASS][22] -> [FAIL][23] ([i915#7084])
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl3/igt@[email protected]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl3/igt@[email protected]* igt@i915_selftest@mock@timelines:
- shard-tglb: NOTRUN -> [INCOMPLETE][24] ([i915#7605])
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@i915_selftest@[email protected]* igt@kms_async_flips@alternate-sync-async-flip@pipe-a-edp-1:
- shard-skl: [PASS][25] -> [FAIL][26] ([i915#2521])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl9/igt@kms_async_flips@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl6/igt@kms_async_flips@[email protected]* igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-180:
- shard-iclb: NOTRUN -> [SKIP][27] ([i915#5286])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_rc_ccs_cc:
- shard-skl: NOTRUN -> [SKIP][28] ([fdo#109271] / [i915#3886]) +3 similar issues
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@kms_ccs@pipe-a-bad-aux-stride-y_tiled_gen12_rc_ccs_cc.html* igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs:
- shard-iclb: NOTRUN -> [SKIP][29] ([fdo#109278] / [i915#3886])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_ccs@pipe-a-bad-pixel-format-y_tiled_gen12_mc_ccs.html* igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs:
- shard-apl: NOTRUN -> [SKIP][30] ([fdo#109271] / [i915#3886])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@kms_ccs@pipe-b-crc-primary-basic-y_tiled_gen12_mc_ccs.html* igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs:
- shard-iclb: NOTRUN -> [SKIP][31] ([fdo#109278]) +7 similar issues
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_ccs@pipe-b-crc-primary-rotation-180-y_tiled_gen12_rc_ccs.html* igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_ccs:
- shard-apl: NOTRUN -> [SKIP][32] ([fdo#109271]) +60 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@kms_ccs@pipe-c-bad-rotation-90-y_tiled_ccs.html* igt@kms_chamelium@dp-audio-edid:
- shard-tglb: NOTRUN -> [SKIP][33] ([fdo#109284] / [fdo#111827])
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]* igt@kms_chamelium@dp-hpd-for-each-pipe:
- shard-iclb: NOTRUN -> [SKIP][34] ([fdo#109284] / [fdo#111827]) +1 similar issue
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@kms_chamelium@hdmi-hpd-for-each-pipe:
- shard-apl: NOTRUN -> [SKIP][35] ([fdo#109271] / [fdo#111827]) +4 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@[email protected]* igt@kms_chamelium@hdmi-mode-timings:
- shard-skl: NOTRUN -> [SKIP][36] ([fdo#109271] / [fdo#111827]) +2 similar issues
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]* igt@kms_content_protection@atomic@pipe-a-dp-1:
- shard-apl: NOTRUN -> [TIMEOUT][37] ([i915#7173])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@kms_content_protection@[email protected]* igt@kms_cursor_crc@cursor-rapid-movement-512x512:
- shard-tglb: NOTRUN -> [SKIP][38] ([i915#3359])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]* igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic:
- shard-iclb: NOTRUN -> [SKIP][39] ([fdo#109274]) +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- shard-iclb: NOTRUN -> [SKIP][40] ([i915#4103])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-tglb: [PASS][41] -> [FAIL][42] ([i915#2346]) +1 similar issue
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb6/igt@kms_cursor_legacy@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@kms_cursor_legacy@[email protected]* igt@kms_flip@flip-vs-expired-vblank@c-edp1:
- shard-skl: [PASS][43] -> [FAIL][44] ([i915#79]) +1 similar issue
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@kms_flip@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl1/igt@kms_flip@[email protected]* igt@kms_flip@plain-flip-fb-recreate-interruptible@b-edp1:
- shard-skl: [PASS][45] -> [FAIL][46] ([i915#2122]) +4 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@kms_flip@[email protected]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl4/igt@kms_flip@[email protected]* igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode:
- shard-iclb: NOTRUN -> [SKIP][47] ([i915#2587] / [i915#2672]) +4 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb6/igt@kms_flip_scaled_crc@flip-32bpp-4tile-to-64bpp-4tile-downscaling@pipe-a-valid-mode.html* igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][48] ([i915#2672] / [i915#3555])
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-32bpp-ytile-to-32bpp-ytilegen12rcccs-downscaling@pipe-a-default-mode.html* igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][49] ([i915#3555]) +1 similar issue
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@kms_flip_scaled_crc@flip-64bpp-xtile-to-16bpp-xtile-downscaling@pipe-a-default-mode.html* igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-upscaling@pipe-a-default-mode:
- shard-iclb: NOTRUN -> [SKIP][50] ([i915#2672]) +4 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb3/igt@kms_flip_scaled_crc@flip-64bpp-yftile-to-32bpp-yftile-upscaling@pipe-a-default-mode.html* igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-shrfb-pgflip-blt:
- shard-iclb: NOTRUN -> [SKIP][51] ([fdo#109280]) +8 similar issues
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-2p-primscrn-shrfb-pgflip-blt.html* igt@kms_frontbuffer_tracking@fbcpsr-modesetfrombusy:
- shard-tglb: NOTRUN -> [SKIP][52] ([i915#6497]) +1 similar issue
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@[email protected]* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-skl: NOTRUN -> [SKIP][53] ([fdo#109271]) +40 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]* igt@kms_plane_alpha_blend@alpha-opaque-fb@pipe-a-dp-1:
- shard-apl: NOTRUN -> [FAIL][54] ([i915#4573]) +2 similar issues
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@kms_plane_alpha_blend@[email protected]* igt@kms_plane_scaling@planes-upscale-factor-0-25@pipe-a-edp-1:
- shard-skl: [PASS][55] -> [DMESG-WARN][56] ([i915#1982])
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl10/igt@kms_plane_scaling@[email protected]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl3/igt@kms_plane_scaling@[email protected]* igt@kms_psr2_sf@overlay-plane-move-continuous-exceed-fully-sf:
- shard-apl: NOTRUN -> [SKIP][57] ([fdo#109271] / [i915#658]) +1 similar issue
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@[email protected]* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-skl: NOTRUN -> [SKIP][58] ([fdo#109271] / [i915#658]) +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]* igt@kms_psr2_su@page_flip-xrgb8888:
- shard-iclb: NOTRUN -> [SKIP][59] ([fdo#109642] / [fdo#111068] / [i915#658]) +1 similar issue
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_psr2_su@page_flip-xrgb8888.html* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][60] -> [SKIP][61] ([fdo#109441])
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_psr@psr2_primary_page_flip.html* igt@kms_scaling_modes@scaling-mode-none@edp-1-pipe-b:
- shard-iclb: NOTRUN -> [SKIP][62] ([i915#5030]) +2 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@kms_scaling_modes@[email protected]* igt@perf@gen12-oa-tlb-invalidate:
- shard-iclb: NOTRUN -> [SKIP][63] ([fdo#109289])
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@sysfs_clients@recycle:
- shard-iclb: NOTRUN -> [SKIP][64] ([i915#2994])
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb8/igt@[email protected]* igt@sysfs_clients@sema-10:
- shard-skl: NOTRUN -> [SKIP][65] ([fdo#109271] / [i915#2994])
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]* igt@sysfs_heartbeat_interval@mixed@vecs0:
- shard-skl: [PASS][66] -> [FAIL][67] ([i915#1731])
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@sysfs_heartbeat_interval@[email protected]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl4/igt@sysfs_heartbeat_interval@[email protected]#### Possible fixes ####
* igt@drm_read@empty-block:
- {shard-rkl}: [SKIP][68] ([i915#1845] / [i915#4098]) -> [PASS][69] +7 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-2/igt@[email protected]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-6/igt@[email protected]* igt@fbdev@unaligned-read:
- {shard-rkl}: [SKIP][70] ([i915#2582]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-2/igt@[email protected]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-6/igt@[email protected]* igt@gem_ctx_isolation@preservation-s3@bcs0:
- shard-apl: [DMESG-WARN][72] ([i915#180]) -> [PASS][73]
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl6/igt@gem_ctx_isolation@[email protected]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl7/igt@gem_ctx_isolation@[email protected]* igt@gem_eio@in-flight-suspend:
- {shard-rkl}: [FAIL][74] ([fdo#103375]) -> [PASS][75]
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]* igt@gem_eio@reset-stress:
- {shard-dg1}: [FAIL][76] ([i915#5784]) -> [PASS][77]
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-dg1-19/igt@[email protected]
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-dg1-15/igt@[email protected]* igt@gem_exec_balancer@parallel-bb-first:
- shard-iclb: [SKIP][78] ([i915#4525]) -> [PASS][79]
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb6/igt@[email protected]
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@[email protected]* igt@gem_exec_fair@basic-flow@rcs0:
- shard-tglb: [FAIL][80] ([i915#2842]) -> [PASS][81]
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb7/igt@gem_exec_fair@[email protected]
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb5/igt@gem_exec_fair@[email protected]* igt@gem_exec_fair@basic-pace-solo@rcs0:
- shard-apl: [FAIL][82] ([i915#2842]) -> [PASS][83]
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl8/igt@gem_exec_fair@[email protected]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl3/igt@gem_exec_fair@[email protected]* igt@gem_exec_fair@basic-pace@vcs0:
- shard-iclb: [FAIL][84] ([i915#2842]) -> [PASS][85]
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@gem_exec_fair@[email protected]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@gem_exec_fair@[email protected]* igt@gem_exec_reloc@basic-wc-cpu:
- {shard-rkl}: [SKIP][86] ([i915#3281]) -> [PASS][87] +2 similar issues
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]* igt@gem_exec_whisper@basic-contexts-priority:
- {shard-rkl}: [FAIL][88] -> [PASS][89]
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-5/igt@[email protected]
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-3/igt@[email protected]* igt@gem_readwrite@read-write:
- {shard-rkl}: [SKIP][90] ([i915#3282]) -> [PASS][91] +1 similar issue
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]* igt@gen9_exec_parse@allowed-single:
- shard-apl: [DMESG-WARN][92] ([i915#5566] / [i915#716]) -> [PASS][93]
[92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl2/igt@[email protected]
[93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl1/igt@[email protected]* igt@gen9_exec_parse@bb-start-far:
- {shard-rkl}: [SKIP][94] ([i915#2527]) -> [PASS][95]
[94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-4/igt@[email protected]
[95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-5/igt@[email protected]* igt@i915_pm_dc@dc9-dpms:
- shard-iclb: [SKIP][96] ([i915#4281]) -> [PASS][97]
[96]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@[email protected]
[97]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb6/igt@[email protected]* igt@i915_selftest@live@gt_heartbeat:
- shard-skl: [DMESG-FAIL][98] ([i915#5334]) -> [PASS][99]
[98]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl4/igt@i915_selftest@live@gt_heartbeat.html
[99]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl7/igt@i915_selftest@live@gt_heartbeat.html* igt@kms_flip@flip-vs-expired-vblank-interruptible@a-edp1:
- shard-skl: [FAIL][100] ([i915#79]) -> [PASS][101]
[100]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl7/igt@kms_flip@[email protected]
[101]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@kms_flip@[email protected]* igt@kms_flip@flip-vs-suspend@c-edp1:
- shard-tglb: [DMESG-WARN][102] ([i915#2411] / [i915#2867]) -> [PASS][103]
[102]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-tglb8/igt@kms_flip@[email protected]
[103]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-tglb6/igt@kms_flip@[email protected]* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-render:
- {shard-rkl}: [SKIP][104] ([i915#1849] / [i915#4098]) -> [PASS][105] +6 similar issues
[104]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-rkl-2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-render.html
[105]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-render.html* igt@kms_psr@psr2_sprite_mmap_cpu:
- shard-iclb: [SKIP][106] ([fdo#109441]) -> [PASS][107] +1 similar issue
[106]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb3/igt@kms_psr@psr2_sprite_mmap_cpu.html
[107]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_cpu.html* igt@perf@polling:
- shard-skl: [FAIL][108] ([i915#1542]) -> [PASS][109]
[108]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl9/igt@[email protected]
[109]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl1/igt@[email protected]#### Warnings ####
* igt@i915_pm_dc@dc3co-vpb-simulation:
- shard-iclb: [SKIP][110] ([i915#658]) -> [SKIP][111] ([i915#588])
[110]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb6/igt@[email protected]
[111]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@[email protected]* igt@kms_plane_alpha_blend@alpha-basic@pipe-c-dp-1:
- shard-apl: [FAIL][112] ([i915#4573]) -> [DMESG-FAIL][113] ([IGT#6]) +1 similar issue
[112]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl6/igt@kms_plane_alpha_blend@[email protected]
[113]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl2/igt@kms_plane_alpha_blend@[email protected]* igt@kms_psr2_sf@overlay-plane-update-continuous-sf:
- shard-iclb: [SKIP][114] ([fdo#111068] / [i915#658]) -> [SKIP][115] ([i915#2920])
[114]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb6/igt@[email protected]
[115]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb2/igt@[email protected]* igt@kms_psr2_sf@overlay-plane-update-sf-dmg-area:
- shard-iclb: [SKIP][116] ([i915#2920]) -> [SKIP][117] ([fdo#111068] / [i915#658])
[116]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-iclb2/igt@[email protected]
[117]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-iclb6/igt@[email protected]* igt@runner@aborted:
- shard-apl: ([FAIL][118], [FAIL][119], [FAIL][120], [FAIL][121]) ([fdo#109271] / [i915#180] / [i915#3002] / [i915#4312]) -> ([FAIL][122], [FAIL][123]) ([i915#3002] / [i915#4312])
[118]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl6/igt@[email protected]
[119]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl7/igt@[email protected]
[120]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl1/igt@[email protected]
[121]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-apl2/igt@[email protected]
[122]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl2/igt@[email protected]
[123]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-apl8/igt@[email protected]
- shard-skl: [FAIL][124] ([i915#6949]) -> ([FAIL][125], [FAIL][126], [FAIL][127]) ([i915#3002] / [i915#4312] / [i915#6949])
[124]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12440/shard-skl1/igt@[email protected]
[125]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl10/igt@[email protected]
[126]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl3/igt@[email protected]
[127]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/shard-skl9/igt@[email protected]{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).[IGT#6]: https://gitlab.freedesktop.org/drm/igt-gpu-tools/issues/6
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109278]: https://bugs.freedesktop.org/show_bug.cgi?id=109278
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109284]: https://bugs.freedesktop.org/show_bug.cgi?id=109284
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109308]: https://bugs.freedesktop.org/show_bug.cgi?id=109308
[fdo#109313]: https://bugs.freedesktop.org/show_bug.cgi?id=109313
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111656]: https://bugs.freedesktop.org/show_bug.cgi?id=111656
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112054]: https://bugs.freedesktop.org/show_bug.cgi?id=112054
[fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#1722]: https://gitlab.freedesktop.org/drm/intel/issues/1722
[i915#1731]: https://gitlab.freedesktop.org/drm/intel/issues/1731
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1804]: https://gitlab.freedesktop.org/drm/intel/issues/1804
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1982]: https://gitlab.freedesktop.org/drm/intel/issues/1982
[i915#2122]: https://gitlab.freedesktop.org/drm/intel/issues/2122
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2411]: https://gitlab.freedesktop.org/drm/intel/issues/2411
[i915#2521]: https://gitlab.freedesktop.org/drm/intel/issues/2521
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#280]: https://gitlab.freedesktop.org/drm/intel/issues/280
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#2867]: https://gitlab.freedesktop.org/drm/intel/issues/2867
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3002]: https://gitlab.freedesktop.org/drm/intel/issues/3002
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3458]: https://gitlab.freedesktop.org/drm/intel/issues/3458
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3539]: https://gitlab.freedesktop.org/drm/intel/issues/3539
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3840]: https://gitlab.freedesktop.org/drm/intel/issues/3840
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#3938]: https://gitlab.freedesktop.org/drm/intel/issues/3938
[i915#3989]: https://gitlab.freedesktop.org/drm/intel/issues/3989
[i915#4036]: https://gitlab.freedesktop.org/drm/intel/issues/4036
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4077]: https://gitlab.freedesktop.org/drm/intel/issues/4077
[i915#4083]: https://gitlab.freedesktop.org/drm/intel/issues/4083
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4171]: https://gitlab.freedesktop.org/drm/intel/issues/4171
[i915#4258]: https://gitlab.freedesktop.org/drm/intel/issues/4258
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4525]: https://gitlab.freedesktop.org/drm/intel/issues/4525
[i915#4538]: https://gitlab.freedesktop.org/drm/intel/issues/4538
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#4573]: https://gitlab.freedesktop.org/drm/intel/issues/4573
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#4833]: https://gitlab.freedesktop.org/drm/intel/issues/4833
[i915#4852]: https://gitlab.freedesktop.org/drm/intel/issues/4852
[i915#4860]: https://gitlab.freedesktop.org/drm/intel/issues/4860
[i915#4873]: https://gitlab.freedesktop.org/drm/intel/issues/4873
[i915#4881]: https://gitlab.freedesktop.org/drm/intel/issues/4881
[i915#4936]: https://gitlab.freedesktop.org/drm/intel/issues/4936
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5030]: https://gitlab.freedesktop.org/drm/intel/issues/5030
[i915#5099]: https://gitlab.freedesktop.org/drm/intel/issues/5099
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5288]: https://gitlab.freedesktop.org/drm/intel/issues/5288
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5461]: https://gitlab.freedesktop.org/drm/intel/issues/5461
[i915#5566]: https://gitlab.freedesktop.org/drm/intel/issues/5566
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#588]: https://gitlab.freedesktop.org/drm/intel/issues/588
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6227]: https://gitlab.freedesktop.org/drm/intel/issues/6227
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6334]: https://gitlab.freedesktop.org/drm/intel/issues/6334
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#6537]: https://gitlab.freedesktop.org/drm/intel/issues/6537
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6949]: https://gitlab.freedesktop.org/drm/intel/issues/6949
[i915#7084]: https://gitlab.freedesktop.org/drm/intel/issues/7084
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#7173]: https://gitlab.freedesktop.org/drm/intel/issues/7173
[i915#7605]: https://gitlab.freedesktop.org/drm/intel/issues/7605
[i915#768]: https://gitlab.freedesktop.org/drm/intel/issues/768
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79Build changes
-------------* Linux:
CI_DRM_12440->Patchwork_111220v2CI-20190529: 20190529
CI_DRM_12440:d21d6474a37e5d43075a24668807ea40a7ee9fc1@git://anongit.freedesktop.org/gfx-ci/linux
IGT_7073:d021d66e389f4a759dc749b5f74f278ecd2e6cbf@ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111220v2:d21d6474a37e5d43075a24668807ea40a7ee9fc1@git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509:fdc5a4ca11124ab8413c7988896eec4c97336694@git://anongit.freedesktop.org/piglit== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v2/index.html
Signature · 4 lines
Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for i915: dedicated MCR locking and hardware semaphore (rev3)
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev3)
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 (rev3)
In reply to Matt Roper== Series Details ==
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev3)
URL : https://patchwork.freedesktop.org/series/111220/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12455 -> Patchwork_111220v3
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_111220v3 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_111220v3, 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_111220v3/index.html
Participating hosts (29 -> 32)
------------------------------
Additional (5): fi-kbl-7567u fi-glk-dsi fi-glk-j4005 fi-kbl-x1275 fi-kbl-8809g
Missing (2): bat-dg1-6 fi-skl-6600u
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_111220v3:
### IGT changes ###
#### Possible regressions ####
* igt@i915_suspend@basic-s2idle-without-i915:
- fi-elk-e7500: [PASS][1] -> [WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-elk-e7500/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-elk-e7500/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_selftest@live@hangcheck:
- {fi-jsl-1}: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-jsl-1/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-jsl-1/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_111220v3 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-kbl-7567u: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#2190])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@[email protected]
- fi-kbl-8809g: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]
- fi-glk-dsi: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#2190])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#2190])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@[email protected]
- fi-kbl-x1275: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#2190])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]
* igt@gem_lmem_swapping@basic:
- fi-glk-j4005: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#4613]) +3 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@[email protected]
- fi-kbl-7567u: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613]) +3 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@[email protected]
* igt@gem_lmem_swapping@verify-random:
- fi-glk-dsi: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4613]) +3 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
- fi-kbl-x1275: NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#4613]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]
* igt@gem_tiled_blits@basic:
- fi-glk-dsi: NOTRUN -> [SKIP][14] ([fdo#109271]) +12 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
* igt@i915_module_load@reload:
- fi-kbl-8809g: NOTRUN -> [DMESG-WARN][15] ([i915#6899])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]
* igt@kms_chamelium@dp-crc-fast:
- fi-glk-dsi: NOTRUN -> [SKIP][16] ([fdo#109271] / [fdo#111827]) +8 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
- fi-kbl-x1275: NOTRUN -> [SKIP][17] ([fdo#109271] / [fdo#111827]) +8 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]
* igt@kms_chamelium@dp-hpd-fast:
- fi-kbl-7567u: NOTRUN -> [SKIP][18] ([fdo#109271] / [fdo#111827]) +8 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@[email protected]
* igt@kms_chamelium@hdmi-crc-fast:
- fi-glk-j4005: NOTRUN -> [SKIP][19] ([fdo#109271] / [fdo#111827]) +8 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@[email protected]
* igt@kms_chamelium@vga-edid-read:
- fi-kbl-8809g: NOTRUN -> [SKIP][20] ([fdo#109271] / [fdo#111827]) +7 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]
* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- fi-kbl-8809g: NOTRUN -> [SKIP][21] ([fdo#109271]) +24 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]
* igt@kms_psr@cursor_plane_move:
- fi-kbl-7567u: NOTRUN -> [SKIP][22] ([fdo#109271]) +30 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@kms_psr@cursor_plane_move.html
* igt@kms_psr@sprite_plane_onoff:
- fi-glk-j4005: NOTRUN -> [SKIP][23] ([fdo#109271]) +9 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@kms_psr@sprite_plane_onoff.html
* igt@prime_vgem@basic-userptr:
- fi-kbl-x1275: NOTRUN -> [SKIP][24] ([fdo#109271]) +10 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]
* igt@runner@aborted:
- fi-kbl-8809g: NOTRUN -> [FAIL][25] ([i915#4312] / [i915#4991])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]
#### Possible fixes ####
* igt@fbdev@write:
- fi-apl-guc: [SKIP][26] ([fdo#109271]) -> [PASS][27] +6 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-apl-guc/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-apl-guc/igt@[email protected]
* igt@gem_exec_suspend@basic-s0@smem:
- {bat-rpls-2}: [DMESG-WARN][28] ([i915#6434]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/bat-rpls-2/igt@gem_exec_suspend@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/bat-rpls-2/igt@gem_exec_suspend@[email protected]
* igt@gem_exec_suspend@basic-s3@smem:
- {bat-rpls-1}: [DMESG-WARN][30] ([i915#6687]) -> [PASS][31]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/bat-rpls-1/igt@gem_exec_suspend@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/bat-rpls-1/igt@gem_exec_suspend@[email protected]
* igt@i915_selftest@live@hangcheck:
- {fi-ehl-2}: [INCOMPLETE][32] ([i915#5153]) -> [PASS][33]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-ehl-2/igt@i915_selftest@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-ehl-2/igt@i915_selftest@[email protected]
* igt@kms_addfb_basic@bad-pitch-0:
- fi-apl-guc: [DMESG-WARN][34] -> [PASS][35] +40 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-apl-guc/igt@[email protected]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-apl-guc/igt@[email protected]
#### Warnings ####
* igt@core_hotunplug@unbind-rebind:
- fi-apl-guc: [DMESG-WARN][36] -> [INCOMPLETE][37] ([i915#7073])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-apl-guc/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-apl-guc/igt@[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#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5153]: https://gitlab.freedesktop.org/drm/intel/issues/5153
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6687]: https://gitlab.freedesktop.org/drm/intel/issues/6687
[i915#6899]: https://gitlab.freedesktop.org/drm/intel/issues/6899
[i915#7073]: https://gitlab.freedesktop.org/drm/intel/issues/7073
Build changes
-------------
* Linux: CI_DRM_12455 -> Patchwork_111220v3
CI-20190529: 20190529
CI_DRM_12455: 1698371742cb7b775e043a383abe49074a305a60 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7076: 888725538e0d6bbb94bbbb1ac278d4afcbbbdad0 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111220v3: 1698371742cb7b775e043a383abe49074a305a60 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
3d875d326e79 drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup 73e2c38d82dc drm/i915/mtl: Add hardware-level lock for steering b0cb4e393073 drm/i915/gt: Add dedicated MCR lock7dd4f5129977 drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes 7657679ea7a2 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_111220v3/index.html
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for i915: dedicated MCR locking and hardware semaphore (rev3)
Quoted 36 lines · Patchwork
== Series Details ==
Series: i915: dedicated MCR locking and hardware semaphore (rev3)
URL : https://patchwork.freedesktop.org/series/111220/
State : failure== Summary ==
CI Bug Log - changes from
CI_DRM_12455->Patchwork_111220v3
====================================================Summary
-------**FAILURE**
Serious unknown changes coming with
Patchwork_111220v3absolutely need to be verified manually.If you think the reported changes have nothing to do with the changes introduced in
Patchwork_111220v3, 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_111220v3/index.html
Participating hosts (29 -> 32)
------------------------------Additional (5): fi-kbl-7567u fi-glk-dsi fi-glk-j4005 fi-kbl-x1275 fi-kbl-8809g
Missing (2): bat-dg1-6 fi-skl-6600uPossible new issues
-------------------Here are the unknown changes that may have been introduced in
Patchwork_111220v3:
Quoted 8 lines
### IGT changes ###
#### Possible regressions ####
* igt@i915_suspend@basic-s2idle-without-i915:
- fi-elk-e7500: [PASS][1] -> [WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-elk-e7500/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-elk-e7500/igt@[email protected]
(i915_suspend:4706) igt_kmod-WARNING: Could not stop 1 audio process(es)
Not related to this series.
Matt
Quoted 168 lines
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* igt@i915_selftest@live@hangcheck:
- {fi-jsl-1}: [PASS][3] -> [INCOMPLETE][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-jsl-1/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-jsl-1/igt@i915_selftest@[email protected]Known issues
------------Here are the changes found in
Patchwork_111220v3that come from known issues:### IGT changes ###
#### Issues hit ####
* igt@gem_huc_copy@huc-copy:
- fi-kbl-7567u: NOTRUN -> [SKIP][5] ([fdo#109271] / [i915#2190])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@[email protected]
- fi-kbl-8809g: NOTRUN -> [SKIP][6] ([fdo#109271] / [i915#2190])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]
- fi-glk-dsi: NOTRUN -> [SKIP][7] ([fdo#109271] / [i915#2190])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
- fi-glk-j4005: NOTRUN -> [SKIP][8] ([fdo#109271] / [i915#2190])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@[email protected]
- fi-kbl-x1275: NOTRUN -> [SKIP][9] ([fdo#109271] / [i915#2190])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]* igt@gem_lmem_swapping@basic:
- fi-glk-j4005: NOTRUN -> [SKIP][10] ([fdo#109271] / [i915#4613]) +3 similar issues
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@[email protected]
- fi-kbl-7567u: NOTRUN -> [SKIP][11] ([fdo#109271] / [i915#4613]) +3 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@[email protected]* igt@gem_lmem_swapping@verify-random:
- fi-glk-dsi: NOTRUN -> [SKIP][12] ([fdo#109271] / [i915#4613]) +3 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
- fi-kbl-x1275: NOTRUN -> [SKIP][13] ([fdo#109271] / [i915#4613]) +3 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]* igt@gem_tiled_blits@basic:
- fi-glk-dsi: NOTRUN -> [SKIP][14] ([fdo#109271]) +12 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]* igt@i915_module_load@reload:
- fi-kbl-8809g: NOTRUN -> [DMESG-WARN][15] ([i915#6899])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]* igt@kms_chamelium@dp-crc-fast:
- fi-glk-dsi: NOTRUN -> [SKIP][16] ([fdo#109271] / [fdo#111827]) +8 similar issues
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-dsi/igt@[email protected]
- fi-kbl-x1275: NOTRUN -> [SKIP][17] ([fdo#109271] / [fdo#111827]) +8 similar issues
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]* igt@kms_chamelium@dp-hpd-fast:
- fi-kbl-7567u: NOTRUN -> [SKIP][18] ([fdo#109271] / [fdo#111827]) +8 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@[email protected]* igt@kms_chamelium@hdmi-crc-fast:
- fi-glk-j4005: NOTRUN -> [SKIP][19] ([fdo#109271] / [fdo#111827]) +8 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@[email protected]* igt@kms_chamelium@vga-edid-read:
- fi-kbl-8809g: NOTRUN -> [SKIP][20] ([fdo#109271] / [fdo#111827]) +7 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]* igt@kms_cursor_legacy@basic-busy-flip-before-cursor:
- fi-kbl-8809g: NOTRUN -> [SKIP][21] ([fdo#109271]) +24 similar issues
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]* igt@kms_psr@cursor_plane_move:
- fi-kbl-7567u: NOTRUN -> [SKIP][22] ([fdo#109271]) +30 similar issues
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-7567u/igt@kms_psr@cursor_plane_move.html* igt@kms_psr@sprite_plane_onoff:
- fi-glk-j4005: NOTRUN -> [SKIP][23] ([fdo#109271]) +9 similar issues
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-glk-j4005/igt@kms_psr@sprite_plane_onoff.html* igt@prime_vgem@basic-userptr:
- fi-kbl-x1275: NOTRUN -> [SKIP][24] ([fdo#109271]) +10 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-x1275/igt@[email protected]* igt@runner@aborted:
- fi-kbl-8809g: NOTRUN -> [FAIL][25] ([i915#4312] / [i915#4991])
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-kbl-8809g/igt@[email protected]#### Possible fixes ####
* igt@fbdev@write:
- fi-apl-guc: [SKIP][26] ([fdo#109271]) -> [PASS][27] +6 similar issues
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-apl-guc/igt@[email protected]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-apl-guc/igt@[email protected]* igt@gem_exec_suspend@basic-s0@smem:
- {bat-rpls-2}: [DMESG-WARN][28] ([i915#6434]) -> [PASS][29]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/bat-rpls-2/igt@gem_exec_suspend@[email protected]
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/bat-rpls-2/igt@gem_exec_suspend@[email protected]* igt@gem_exec_suspend@basic-s3@smem:
- {bat-rpls-1}: [DMESG-WARN][30] ([i915#6687]) -> [PASS][31]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/bat-rpls-1/igt@gem_exec_suspend@[email protected]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/bat-rpls-1/igt@gem_exec_suspend@[email protected]* igt@i915_selftest@live@hangcheck:
- {fi-ehl-2}: [INCOMPLETE][32] ([i915#5153]) -> [PASS][33]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-ehl-2/igt@i915_selftest@[email protected]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-ehl-2/igt@i915_selftest@[email protected]* igt@kms_addfb_basic@bad-pitch-0:
- fi-apl-guc: [DMESG-WARN][34] -> [PASS][35] +40 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-apl-guc/igt@[email protected]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-apl-guc/igt@[email protected]#### Warnings ####
* igt@core_hotunplug@unbind-rebind:
- fi-apl-guc: [DMESG-WARN][36] -> [INCOMPLETE][37] ([i915#7073])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12455/fi-apl-guc/igt@[email protected]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/fi-apl-guc/igt@[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#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#2190]: https://gitlab.freedesktop.org/drm/intel/issues/2190
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4991]: https://gitlab.freedesktop.org/drm/intel/issues/4991
[i915#5153]: https://gitlab.freedesktop.org/drm/intel/issues/5153
[i915#6434]: https://gitlab.freedesktop.org/drm/intel/issues/6434
[i915#6687]: https://gitlab.freedesktop.org/drm/intel/issues/6687
[i915#6899]: https://gitlab.freedesktop.org/drm/intel/issues/6899
[i915#7073]: https://gitlab.freedesktop.org/drm/intel/issues/7073Build changes
-------------* Linux:
CI_DRM_12455->Patchwork_111220v3CI-20190529: 20190529
CI_DRM_12455:1698371742cb7b775e043a383abe49074a305a60@git://anongit.freedesktop.org/gfx-ci/linux
IGT_7076:888725538e0d6bbb94bbbb1ac278d4afcbbbdad0@ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_111220v3:1698371742cb7b775e043a383abe49074a305a60@git://anongit.freedesktop.org/gfx-ci/linux### Linux commits
3d875d326e79drm/i915/mtl: Hold forcewake and MCR lock over PPAT setup73e2c38d82dcdrm/i915/mtl: Add hardware-level lock for steeringb0cb4e393073drm/i915/gt: Add dedicated MCR lock7dd4f5129977drm/i915/gt: Pass gt rather than uncore to lowest-level reads/writes7657679ea7a2drm/i915/gt: Correct kerneldoc forintel_gt_mcr_wait_for_reg()== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_111220v3/index.html
Signature · 4 lines
Matt Roper Graphics Software Engineer VTT-OSGC Platform Enablement Intel Corporation