drm/i915: Make IRQ reset and postinstall multi-gt aware
Subsystems (2)
PATCH v2 1/1 drm/i915: Make IRQ reset and postinstall multi-gt aware
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
---
Hi,
proposing again this patch, apparently GuC needs this patch to initialize the media GT.
Andi
Changelog
=========
v1 -> v2
- improve description in the commit log.
drivers/gpu/drm/i915/i915_irq.c | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/i915_irq.c +18 -10
@@ -2764,14 +2764,19 @@ static void dg1_irq_reset(struct drm_i915_private *dev_priv) {struct intel_gt *gt =to_gt (dev_priv);struct intel_uncore *uncore = gt->uncore; +unsigned int i;dg1_master_intr_disable (dev_priv->uncore.regs); -gen11_gt_irq_reset (gt); -gen11_display_irq_reset (dev_priv); +for_each_gt (gt, dev_priv, i) { +gen11_gt_irq_reset (gt); -GEN3_IRQ_RESET (uncore,GEN11_GU_MISC_ ); -GEN3_IRQ_RESET (uncore,GEN8_PCU_ ); + uncore = gt->uncore; +GEN3_IRQ_RESET (uncore,GEN11_GU_MISC_ ); +GEN3_IRQ_RESET (uncore,GEN8_PCU_ ); + } + +gen11_display_irq_reset (dev_priv); } void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv,
@@ -3425,13 +3430,16 @@ static void gen11_irq_postinstall(struct drm_i915_private *dev_priv)static void dg1_irq_postinstall (struct drm_i915_private *dev_priv) { -struct intel_gt *gt =to_gt (dev_priv); -struct intel_uncore *uncore = gt->uncore;u32 gu_misc_masked =GEN11_GU_MISC_GSE ; +struct intel_gt *gt; +unsigned int i; -gen11_gt_irq_postinstall (gt); +for_each_gt (gt, dev_priv, i) { +gen11_gt_irq_postinstall (gt); -GEN3_IRQ_INIT (uncore,GEN11_GU_MISC_ , ~gu_misc_masked, gu_misc_masked); +GEN3_IRQ_INIT (gt->uncore,GEN11_GU_MISC_ , ~gu_misc_masked, + gu_misc_masked); + }if (HAS_DISPLAY (dev_priv)) {icp_irq_postinstall (dev_priv);
@@ -3440,8 +3448,8 @@ static void dg1_irq_postinstall(struct drm_i915_private *dev_priv) GEN11_DISPLAY_IRQ_ENABLE); } -dg1_master_intr_enable (uncore->regs); -intel_uncore_posting_read (uncore,DG1_MSTR_TILE_INTR ); +dg1_master_intr_enable (to_gt (dev_priv)->uncore->regs); +intel_uncore_posting_read (to_gt (dev_priv)->uncore,DG1_MSTR_TILE_INTR ); }static void cherryview_irq_postinstall (struct drm_i915_private *dev_priv)
Signature · 1 line
2.39.2
Quoted 9 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Quoted 8 lines
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,proposing again this patch, apparently GuC needs this patch to initialize the media GT.
What is the resolution for Matt's concern that this is wrong for MTL?
Regards,
Tvrtko
Quoted 68 lines
Changelog
=========
v1 -> v2
- improve description in the commit log.drivers/gpu/drm/i915/i915_irq.c | 28 ++++++++++++++++++---------- 1 file changed, 18 insertions(+), 10 deletions(-)drivers/gpu/drm/i915/i915_irq.c +18
-10@@ -2764,14 +2764,19 @@ static void dg1_irq_reset(struct drm_i915_private *dev_priv) {struct intel_gt *gt =to_gt (dev_priv);struct intel_uncore *uncore = gt->uncore; +unsigned int i;dg1_master_intr_disable (dev_priv->uncore.regs); -gen11_gt_irq_reset (gt); -gen11_display_irq_reset (dev_priv); +for_each_gt (gt, dev_priv, i) { +gen11_gt_irq_reset (gt); -GEN3_IRQ_RESET (uncore,GEN11_GU_MISC_ ); -GEN3_IRQ_RESET (uncore,GEN8_PCU_ ); + uncore = gt->uncore; +GEN3_IRQ_RESET (uncore,GEN11_GU_MISC_ ); +GEN3_IRQ_RESET (uncore,GEN8_PCU_ ); + } + +gen11_display_irq_reset (dev_priv); } void gen8_irq_power_well_post_enable(struct drm_i915_private *dev_priv,@@ -3425,13 +3430,16 @@ static void gen11_irq_postinstall(struct drm_i915_private *dev_priv)static void dg1_irq_postinstall (struct drm_i915_private *dev_priv) { -struct intel_gt *gt =to_gt (dev_priv); -struct intel_uncore *uncore = gt->uncore;u32 gu_misc_masked =GEN11_GU_MISC_GSE ; +struct intel_gt *gt; +unsigned int i; -gen11_gt_irq_postinstall (gt); +for_each_gt (gt, dev_priv, i) { +gen11_gt_irq_postinstall (gt); -GEN3_IRQ_INIT (uncore,GEN11_GU_MISC_ , ~gu_misc_masked, gu_misc_masked); +GEN3_IRQ_INIT (gt->uncore,GEN11_GU_MISC_ , ~gu_misc_masked, + gu_misc_masked); + }if (HAS_DISPLAY (dev_priv)) {icp_irq_postinstall (dev_priv);@@ -3440,8 +3448,8 @@ static void dg1_irq_postinstall(struct drm_i915_private *dev_priv) GEN11_DISPLAY_IRQ_ENABLE); } -dg1_master_intr_enable (uncore->regs); -intel_uncore_posting_read (uncore,DG1_MSTR_TILE_INTR ); +dg1_master_intr_enable (to_gt (dev_priv)->uncore->regs); +intel_uncore_posting_read (to_gt (dev_priv)->uncore,DG1_MSTR_TILE_INTR ); }static void cherryview_irq_postinstall (struct drm_i915_private *dev_priv)
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 17 lines · Tvrtko Ursulin
Quoted 15 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,
Quoted 4 lines
Quoted 2 lines
proposing again this patch, apparently GuC needs this patch to initialize the media GT.
What is the resolution for Matt's concern that this is wrong for MTL?
There are two explanations, one easy and one less easy.
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
Thanks,
Andi
(*)
[drm] *ERROR* GT1: GUC: CT: No response for request 0x550a (fence 7) [drm] *ERROR* GT1: GUC: CT: Sending action 0x550a failed (-ETIMEDOUT) status=0X0 [drm] *ERROR* GT1: GUC: Failed to enable usage stats: -ETIMEDOUT [drm] *ERROR* GT1: GuC initialization failed -ETIMEDOUT
[drm] *ERROR* GT1: Enabling uc failed (-5)
[drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged!
Quoted 29 lines · Andi Shyti
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 17 lines · Tvrtko Ursulin
Quoted 15 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,Quoted 4 lines
Quoted 2 lines
proposing again this patch, apparently GuC needs this patch to initialize the media GT.
What is the resolution for Matt's concern that this is wrong for MTL?
There are two explanations, one easy and one less easy.
Quoted 8 lines
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
I see. It does not sound too challenging to handle with a little bit of refactoring. Move writes engine registers to a helper and add a MTL specific reset/postinstall? Then MTL can do the engine ones outside the for_each_gt loop and the replicated ones under it. Give or take, I did not look into the details.
Regards,
Tvrtko
Quoted 27 lines · Andi Shyti
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 17 lines · Tvrtko Ursulin
Quoted 15 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,Quoted 4 lines
Quoted 2 lines
proposing again this patch, apparently GuC needs this patch to initialize the media GT.
What is the resolution for Matt's concern that this is wrong for MTL?
Quoted 7 lines
There are two explanations, one easy and one less easy.
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
Assuming you're talking about MTL_GUC_MGUC_INTR_MASK, that's not true; it's just a single sgunit register (0x1900e8) that has different bitfields for the primary GuC and the media GuC. So I still think we should avoid looping over GTs; it's actually much simpler to handle things in a single pass since we can just determine the single register value once (all fields) and write it directly, instead of doing two separate RMW updates to the same register to try to avoid clobbering the other GuC's settings.
For pre-MTL platforms, it's the same register, except that the bitfield now devoted to the media GuC was previously used for something else (scatter/gather).
Matt
Quoted 15 lines
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
Thanks,
Andi(*)
[drm] *ERROR* GT1: GUC: CT: No response for request0x550a(fence 7) [drm] *ERROR* GT1: GUC: CT: Sending action0x550afailed (-ETIMEDOUT) status=0X0 [drm] *ERROR* GT1: GUC: Failed to enable usage stats:-ETIMEDOUT[drm] *ERROR* GT1: GuC initialization failed-ETIMEDOUT
[drm] *ERROR* GT1: Enabling uc failed (-5)
[drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged!
Signature · 4 lines
Matt Roper Graphics Software Engineer Linux GPU Platform Enablement Intel Corporation
Quoted 41 lines · Matt Roper
Quoted 23 lines · Andi Shyti
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 18 lines · Tvrtko Ursulin
Quoted 17 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,proposing again this patch, apparently GuC needs this patch to initialize the media GT.
Quoted 8 lines
Quoted 1 line
What is the resolution for Matt's concern that this is wrong for MTL?
There are two explanations, one easy and one less easy.
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
Assuming you're talking about
MTL_GUC_MGUC_INTR_MASK, that's not true; it's just a single sgunit register (0x1900e8) that has different bitfields for the primary GuC and the media GuC. So I still think we should avoid looping over GTs; it's actually much simpler to handle things in a single pass since we can just determine the single register value once (all fields) and write it directly, instead of doing two separate RMW updates to the same register to try to avoid clobbering the other GuC's settings.
Quoted 3 lines
For pre-MTL platforms, it's the same register, except that the bitfield now devoted to the media GuC was previously used for something else (scatter/gather).
It's not just the GuC, the VCS/VECS engine programming is also tied to the media GT (via the HAS_ENGINE checks). It looks like we unconditionally program VCS 0 and 2, so it'll still work for MTL, but if we get a device with more VCS engines it'll break. Maybe we can add a MTL version of the function that just programs everything unconditionally? Going forward it should be ok to program things for engines that don't exist, but I'm not sure we can do that for older platforms that came before the extra engines were ever defined in HW.
Daniele
Quoted 18 lines
Matt
Quoted 14 lines
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
Thanks,
Andi(*)
[drm] *ERROR* GT1: GUC: CT: No response for request0x550a(fence 7) [drm] *ERROR* GT1: GUC: CT: Sending action0x550afailed (-ETIMEDOUT) status=0X0 [drm] *ERROR* GT1: GUC: Failed to enable usage stats:-ETIMEDOUT[drm] *ERROR* GT1: GuC initialization failed-ETIMEDOUT
[drm] *ERROR* GT1: Enabling uc failed (-5)
[drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged!
Quoted 35 lines · Daniele
Quoted 32 lines · Matt Roper
Quoted 31 lines · Andi Shyti
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 16 lines · Tvrtko Ursulin
Quoted 15 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,Quoted 3 lines
Quoted 2 lines
proposing again this patch, apparently GuC needs this patch to initialize the media GT.
What is the resolution for Matt's concern that this is wrong for MTL?
There are two explanations, one easy and one less easy.
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
Quoted 8 lines
Quoted 8 lines
Assuming you're talking about
MTL_GUC_MGUC_INTR_MASK, that's not true; it's just a single sgunit register (0x1900e8) that has different bitfields for the primary GuC and the media GuC. So I still think we should avoid looping over GTs; it's actually much simpler to handle things in a single pass since we can just determine the single register value once (all fields) and write it directly, instead of doing two separate RMW updates to the same register to try to avoid clobbering the other GuC's settings.
if we handle exceptions in a single pass wouldn't we have many exceptions to handle in the long run?
Quoted 4 lines
Quoted 3 lines
For pre-MTL platforms, it's the same register, except that the bitfield now devoted to the media GuC was previously used for something else (scatter/gather).
Quoted 8 lines
It's not just the GuC, the VCS/VECS engine programming is also tied to the media GT (via the
HAS_ENGINEchecks). It looks like we unconditionally program VCS 0 and 2, so it'll still work for MTL, but if we get a device with more VCS engines it'll break. Maybe we can add a MTL version of the function that just programs everything unconditionally? Going forward it should be ok to program things for engines that don't exist, but I'm not sure we can do that for older platforms that came before the extra engines were ever defined in HW.
This is more or less what Tvrtko has suggested, as well. Looks to me like replicating some code... anyway, I will try and see how it looks like.
Andi
PS Thanks Matt, Daniele and Tvrtko for the feedback.
Quoted 20 lines
Daniele
Quoted 18 lines
Matt
Quoted 14 lines
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
Thanks,
Andi(*)
[drm] *ERROR* GT1: GUC: CT: No response for request0x550a(fence 7) [drm] *ERROR* GT1: GUC: CT: Sending action0x550afailed (-ETIMEDOUT) status=0X0 [drm] *ERROR* GT1: GUC: Failed to enable usage stats:-ETIMEDOUT[drm] *ERROR* GT1: GuC initialization failed-ETIMEDOUT
[drm] *ERROR* GT1: Enabling uc failed (-5)
[drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged!
Quoted 45 lines · Andi Shyti
Quoted 35 lines · Daniele
Quoted 32 lines · Matt Roper
Quoted 31 lines · Andi Shyti
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 16 lines · Tvrtko Ursulin
Quoted 15 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,Quoted 3 lines
Quoted 2 lines
proposing again this patch, apparently GuC needs this patch to initialize the media GT.
What is the resolution for Matt's concern that this is wrong for MTL?
There are two explanations, one easy and one less easy.
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
Quoted 8 lines
Quoted 8 lines
Assuming you're talking about
MTL_GUC_MGUC_INTR_MASK, that's not true; it's just a single sgunit register (0x1900e8) that has different bitfields for the primary GuC and the media GuC. So I still think we should avoid looping over GTs; it's actually much simpler to handle things in a single pass since we can just determine the single register value once (all fields) and write it directly, instead of doing two separate RMW updates to the same register to try to avoid clobbering the other GuC's settings.
Quoted 2 lines
if we handle exceptions in a single pass wouldn't we have many exceptions to handle in the long run?
I don't think so, it basically boils down to something along the lines of
if (MEDIA_VER(i915) >= 13)
val = HIGH_BITS | LOW_BITS;
else
val = HIGH_BITS;
...
intel_uncore_write(val);which isn't really any more complicated than today's logic:
called for each gt {
...
if (gt is MEDIA)
bits = LOW_BITS;
else
bits = HIGH_BITS;
...
intel_uncore_rmw(bits);
}Matt
Quoted 42 lines
Quoted 5 lines
Quoted 4 lines
For pre-MTL platforms, it's the same register, except that the bitfield now devoted to the media GuC was previously used for something else (scatter/gather).
Quoted 8 lines
It's not just the GuC, the VCS/VECS engine programming is also tied to the media GT (via the
HAS_ENGINEchecks). It looks like we unconditionally program VCS 0 and 2, so it'll still work for MTL, but if we get a device with more VCS engines it'll break. Maybe we can add a MTL version of the function that just programs everything unconditionally? Going forward it should be ok to program things for engines that don't exist, but I'm not sure we can do that for older platforms that came before the extra engines were ever defined in HW.This is more or less what Tvrtko has suggested, as well. Looks to me like replicating some code... anyway, I will try and see how it looks like.
Andi
PS Thanks Matt, Daniele and Tvrtko for the feedback.
Quoted 20 lines
Daniele
Quoted 18 lines
Matt
Quoted 14 lines
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
Thanks,
Andi(*)
[drm] *ERROR* GT1: GUC: CT: No response for request0x550a(fence 7) [drm] *ERROR* GT1: GUC: CT: Sending action0x550afailed (-ETIMEDOUT) status=0X0 [drm] *ERROR* GT1: GUC: Failed to enable usage stats:-ETIMEDOUT[drm] *ERROR* GT1: GuC initialization failed-ETIMEDOUT
[drm] *ERROR* GT1: Enabling uc failed (-5)
[drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged!
Signature · 4 lines
Matt Roper Graphics Software Engineer Linux GPU Platform Enablement Intel Corporation
Quoted 48 lines · Daniele
Quoted 41 lines · Matt Roper
Quoted 23 lines · Andi Shyti
Hi Tvrtko,
(I forgot to CC Daniele)
Quoted 18 lines · Tvrtko Ursulin
Quoted 17 lines · Andi Shyti
From: Paulo Zanoni <[email protected]>
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,proposing again this patch, apparently GuC needs this patch to initialize the media GT.
Quoted 8 lines
Quoted 1 line
What is the resolution for Matt's concern that this is wrong for MTL?
There are two explanations, one easy and one less easy.
The easy one: without this patch i915 doesn't boot on MTL!(*)
The second explanation is that in MTL the media engine has it's own set of misc irq's registers and those are on a different GT (Daniele pointed this out).
Assuming you're talking about
MTL_GUC_MGUC_INTR_MASK, that's not true; it's just a single sgunit register (0x1900e8) that has different bitfields for the primary GuC and the media GuC. So I still think we should avoid looping over GTs; it's actually much simpler to handle things in a single pass since we can just determine the single register value once (all fields) and write it directly, instead of doing two separate RMW updates to the same register to try to avoid clobbering the other GuC's settings.Quoted 3 lines
For pre-MTL platforms, it's the same register, except that the bitfield now devoted to the media GuC was previously used for something else (scatter/gather).
Quoted 8 lines
It's not just the GuC, the VCS/VECS engine programming is also tied to the media GT (via the
HAS_ENGINEchecks). It looks like we unconditionally program VCS 0 and 2, so it'll still work for MTL, but if we get a device with more VCS engines it'll break. Maybe we can add a MTL version of the function that just programs everything unconditionally? Going forward it should be ok to program things for engines that don't exist, but I'm not sure we can do that for older platforms that came before the extra engines were ever defined in HW.
Right, so I think the engine handling is already correct for MTL today; the main concern would be how it might need to change for other future platforms if more media engines show back up on a media GT. I think we can wait and cross that bridge if/when we get to it. With focus moving over to the Xe KMD, we might be on a completely different driver by the time the hardware adds back in more media engines that aren't already covered unconditionally.
Matt
Quoted 22 lines
Daniele
Quoted 18 lines
Matt
Quoted 14 lines
I sent this patch not to bypass any review, but to restart the discussion as this patch was just dropped.
Thanks,
Andi(*)
[drm] *ERROR* GT1: GUC: CT: No response for request0x550a(fence 7) [drm] *ERROR* GT1: GUC: CT: Sending action0x550afailed (-ETIMEDOUT) status=0X0 [drm] *ERROR* GT1: GUC: Failed to enable usage stats:-ETIMEDOUT[drm] *ERROR* GT1: GuC initialization failed-ETIMEDOUT
[drm] *ERROR* GT1: Enabling uc failed (-5)
[drm] *ERROR* GT1: Failed to initialize GPU, declaring it wedged!
Signature · 4 lines
Matt Roper Graphics Software Engineer Linux GPU Platform Enablement Intel Corporation
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Make IRQ reset and postinstall multi-gt aware (rev2)
In reply to Andi Shyti== Series Details ==
== Series Details ==
Series: drm/i915: Make IRQ reset and postinstall multi-gt aware (rev2)
URL : https://patchwork.freedesktop.org/series/115465/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_13000 -> Patchwork_115465v2
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_115465v2 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_115465v2, 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_115465v2/index.html
Participating hosts (37 -> 36)
------------------------------
Missing (1): fi-snb-2520m
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_115465v2:
### IGT changes ###
#### Possible regressions ####
* igt@core_hotunplug@unbind-rebind:
- fi-apl-guc: [PASS][1] -> [ABORT][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13000/fi-apl-guc/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/fi-apl-guc/igt@[email protected]
Known issues
------------
Here are the changes found in Patchwork_115465v2 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rps@basic-api:
- bat-dg2-11: [PASS][3] -> [FAIL][4] ([i915#8308])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13000/bat-dg2-11/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-dg2-11/igt@[email protected]
* igt@i915_selftest@live@slpc:
- bat-rpls-1: NOTRUN -> [DMESG-FAIL][5] ([i915#6367])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-rpls-1/igt@i915_selftest@[email protected]
* igt@kms_chamelium_hpd@common-hpd-after-suspend:
- bat-rpls-1: NOTRUN -> [SKIP][6] ([i915#7828])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-rpls-1/igt@[email protected]
* igt@kms_pipe_crc_basic@nonblocking-crc-frame-sequence@pipe-c-dp-1:
- bat-dg2-8: [PASS][7] -> [FAIL][8] ([i915#7932]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13000/bat-dg2-8/igt@kms_pipe_crc_basic@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-dg2-8/igt@kms_pipe_crc_basic@[email protected]
* igt@kms_pipe_crc_basic@suspend-read-crc:
- bat-rpls-1: NOTRUN -> [SKIP][9] ([i915#1845])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-rpls-1/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@reset:
- bat-rpls-1: [ABORT][10] ([i915#4983]) -> [PASS][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13000/bat-rpls-1/igt@i915_selftest@[email protected]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-rpls-1/igt@i915_selftest@[email protected]
#### Warnings ####
* igt@i915_selftest@live@slpc:
- bat-rpls-2: [DMESG-FAIL][12] ([i915#6997] / [i915#7913]) -> [DMESG-FAIL][13] ([i915#6367] / [i915#7913])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13000/bat-rpls-2/igt@i915_selftest@[email protected]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/bat-rpls-2/igt@i915_selftest@[email protected]
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#6367]: https://gitlab.freedesktop.org/drm/intel/issues/6367
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7828]: https://gitlab.freedesktop.org/drm/intel/issues/7828
[i915#7913]: https://gitlab.freedesktop.org/drm/intel/issues/7913
[i915#7932]: https://gitlab.freedesktop.org/drm/intel/issues/7932
[i915#8308]: https://gitlab.freedesktop.org/drm/intel/issues/8308
Build changes
-------------
* Linux: CI_DRM_13000 -> Patchwork_115465v2
CI-20190529: 20190529
CI_DRM_13000: 5d4d06561ff5328f2e8fa1608434360a1b6de471 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7253: 1a619e8dbc6ca887f2ae24b2d7f1ac536342f58c @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_115465v2: 5d4d06561ff5328f2e8fa1608434360a1b6de471 @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
4cdb0bb094b8 drm/i915: Make IRQ reset and postinstall multi-gt aware
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_115465v2/index.html
Quoted 1 line · Andi Shyti
From: Paulo Zanoni <[email protected]>
Hi
https://en.wikipedia.org/wiki/Ship_of_Theseus
My original patch was written in 2018. Since then, the implementation has been rebased and changed multiple times, the commit message has been changed, the subject line has been changed, yet none of that is documented in the patch's revision history: it was all removed and it now looks like I'm the author of the version that was submitted this month. I never liked this "erase the internal patch's changelog before submitting it upstream for the first time" process, I think it erases crucial information and misleads people.
I know I said something different earlier in private, but after further reflection, I concluded I do not feel comfortable having my name as the Author or as the Signed-off-by in this patch. Please remove it. You can add a "Based-on-patch-by: Paulo Zanoni <[email protected]>" if you want, but that's not necessary.
This should also help in case some bug is bisected to this patch, then I won't need to spend time researching who I should forward the emails to.
Thanks,
Paulo
Quoted 117 lines
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>---
Hi,proposing again this patch, apparently GuC needs this patch to initialize the media GT.
Andi
Changelog
=========
v1 -> v2
- improve description in the commit log.drivers/gpu/drm/i915/i915_irq.c | 28 ++++++++++++++++++----------
1 file changed, 18 insertions(+), 10 deletions(-)drivers/gpu/drm/i915/i915_irq.c +1
-0@@ -2764,14 +2764,19 @@ static void dg1_irq_reset(struct drm_i915_private *dev_priv) { struct intel_gt *gt = to_gt(dev_priv); struct intel_uncore *uncore = gt->uncore; +unsigned int i;
dg1_master_intr_disable(dev_priv->uncore.regs);drivers/gpu/drm/i915/i915_irq.c +2
-2-gen11_gt_irq_reset (gt); -gen11_display_irq_reset (dev_priv); +for_each_gt (gt, dev_priv, i) { +gen11_gt_irq_reset (gt);drivers/gpu/drm/i915/i915_irq.c +6
-2-GEN3_IRQ_RESET (uncore,GEN11_GU_MISC_ ); -GEN3_IRQ_RESET (uncore,GEN8_PCU_ ); + uncore = gt->uncore; +GEN3_IRQ_RESET (uncore,GEN11_GU_MISC_ ); +GEN3_IRQ_RESET (uncore,GEN8_PCU_ ); + } + +gen11_display_irq_reset (dev_priv);}
void gen8_irq_power_well_post_enable(struct
drm_i915_private*dev_priv,drivers/gpu/drm/i915/i915_irq.c +0
-0@@ -3425,13 +3430,16 @@ static void gen11_irq_postinstall(struct drm_i915_private *dev_priv)static void
dg1_irq_postinstall(struct drm_i915_private *dev_priv){drivers/gpu/drm/i915/i915_irq.c +0
-2-struct intel_gt *gt =to_gt (dev_priv); -struct intel_uncore *uncore = gt->uncore;u32
gu_misc_masked=GEN11_GU_MISC_GSE;drivers/gpu/drm/i915/i915_irq.c +2
-0+struct intel_gt *gt; +unsigned int i;drivers/gpu/drm/i915/i915_irq.c +2
-1-gen11_gt_irq_postinstall (gt); +for_each_gt (gt, dev_priv, i) { +gen11_gt_irq_postinstall (gt);drivers/gpu/drm/i915/i915_irq.c +3
-1-GEN3_IRQ_INIT (uncore,GEN11_GU_MISC_ , ~gu_misc_masked, gu_misc_masked); +GEN3_IRQ_INIT (gt->uncore,GEN11_GU_MISC_ , ~gu_misc_masked, + gu_misc_masked); + }if (
HAS_DISPLAY(dev_priv)) {
icp_irq_postinstall(dev_priv);drivers/gpu/drm/i915/i915_irq.c +0
-0@@ -3440,8 +3448,8 @@ static void dg1_irq_postinstall(struct drm_i915_private *dev_priv) GEN11_DISPLAY_IRQ_ENABLE); }drivers/gpu/drm/i915/i915_irq.c +2
-2-dg1_master_intr_enable (uncore->regs); -intel_uncore_posting_read (uncore,DG1_MSTR_TILE_INTR ); +dg1_master_intr_enable (to_gt (dev_priv)->uncore->regs); +intel_uncore_posting_read (to_gt (dev_priv)->uncore,DG1_MSTR_TILE_INTR );}
static void
cherryview_irq_postinstall(struct drm_i915_private *dev_priv)
Hi Paulo,
Quoted 17 lines
https://en.wikipedia.org/wiki/Ship_of_Theseus
My original patch was written in 2018. Since then, the implementation has been rebased and changed multiple times, the commit message has been changed, the subject line has been changed, yet none of that is documented in the patch's revision history: it was all removed and it now looks like I'm the author of the version that was submitted this month. I never liked this "erase the internal patch's changelog before submitting it upstream for the first time" process, I think it erases crucial information and misleads people.
I know I said something different earlier in private, but after further reflection, I concluded I do not feel comfortable having my name as the Author or as the Signed-off-by in this patch. Please remove it. You can add a "Based-on-patch-by: Paulo Zanoni <[email protected]>" if you want, but that's not necessary.
Quoted 3 lines
This should also help in case some bug is bisected to this patch, then I won't need to spend time researching who I should forward the emails to.
Sure! When porting and back porting patches I try to preserve as much as possible the original authorship.
But, if you feel more comfortable, I can take it on me.
Andi
Quoted 14 lines
Thanks,
PauloQuoted 11 lines
In multitile systems IRQ need to be reset and enabled per GT.
Although in MTL the GUnit misc interrupts register set are available only in GT-0, we need to loop through all the GT's in order to initialize the media engine which lies on a different GT.
Signed-off-by Paulo Zanoni <[email protected]>Cc Tvrtko Ursulin <[email protected]>Signed-off-by Andi Shyti <[email protected]>