* [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
@ 2019-10-03 14:02 Ville Syrjala
2019-10-03 14:12 ` Chris Wilson
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Ville Syrjala @ 2019-10-03 14:02 UTC (permalink / raw)
To: intel-gfx
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
The current "disable C3+" workaround for the delayed vblank
irqs on i945gm no longer works. I'm not sure what changed, but
now I need to also disable C2. I also got my hands on a i915gm
machine that suffers from the same issue.
After some furious poking of registers I managed to find a
better workaround: The "Do not Turn off Core Render Clock in C
states" bit. With that I no longer have to disable any C-states,
and as a nice bonus the power cost is only ~1/4 of the
"disable C3+" method (which mind you doesn't even work anymore,
and so would have an even higher power cost if we made it work
by also disabling C2).
So let's throw out all the cpuidle/qos crap and just toggle
the magic bit as needed. And we extend the workaround to cover
i915gm as well.
Cc: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
drivers/gpu/drm/i915/display/intel_display.c | 10 +--
drivers/gpu/drm/i915/i915_drv.h | 9 +--
drivers/gpu/drm/i915/i915_irq.c | 79 +++-----------------
drivers/gpu/drm/i915/i915_irq.h | 4 +-
drivers/gpu/drm/i915/i915_reg.h | 1 +
5 files changed, 22 insertions(+), 81 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
index c3ac5a5c5185..8f077e2d0dfd 100644
--- a/drivers/gpu/drm/i915/display/intel_display.c
+++ b/drivers/gpu/drm/i915/display/intel_display.c
@@ -15092,12 +15092,12 @@ static const struct drm_crtc_funcs i965_crtc_funcs = {
.disable_vblank = i965_disable_vblank,
};
-static const struct drm_crtc_funcs i945gm_crtc_funcs = {
+static const struct drm_crtc_funcs i915gm_crtc_funcs = {
INTEL_CRTC_FUNCS,
.get_vblank_counter = i915_get_vblank_counter,
- .enable_vblank = i945gm_enable_vblank,
- .disable_vblank = i945gm_disable_vblank,
+ .enable_vblank = i915gm_enable_vblank,
+ .disable_vblank = i915gm_disable_vblank,
};
static const struct drm_crtc_funcs i915_crtc_funcs = {
@@ -15168,8 +15168,8 @@ static int intel_crtc_init(struct drm_i915_private *dev_priv, enum pipe pipe)
funcs = &g4x_crtc_funcs;
else if (IS_GEN(dev_priv, 4))
funcs = &i965_crtc_funcs;
- else if (IS_I945GM(dev_priv))
- funcs = &i945gm_crtc_funcs;
+ else if (IS_I945GM(dev_priv) || IS_I915GM(dev_priv))
+ funcs = &i915gm_crtc_funcs;
else if (IS_GEN(dev_priv, 3))
funcs = &i915_crtc_funcs;
else
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 337d8306416a..5a6f2de2c175 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -1730,13 +1730,8 @@ struct drm_i915_private {
struct work_struct idle_work;
} gem;
- /* For i945gm vblank irq vs. C3 workaround */
- struct {
- struct work_struct work;
- struct pm_qos_request pm_qos;
- u8 c3_disable_latency;
- u8 enabled;
- } i945gm_vblank;
+ /* For i915gm/i945gm vblank irq workaround */
+ u8 vblank_enabled;
/* perform PHY state sanity checks? */
bool chv_phy_assert[2];
diff --git a/drivers/gpu/drm/i915/i915_irq.c b/drivers/gpu/drm/i915/i915_irq.c
index bc83f094065a..f2371b6083c6 100644
--- a/drivers/gpu/drm/i915/i915_irq.c
+++ b/drivers/gpu/drm/i915/i915_irq.c
@@ -29,7 +29,6 @@
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
#include <linux/circ_buf.h>
-#include <linux/cpuidle.h>
#include <linux/slab.h>
#include <linux/sysrq.h>
@@ -2910,12 +2909,18 @@ int i8xx_enable_vblank(struct drm_crtc *crtc)
return 0;
}
-int i945gm_enable_vblank(struct drm_crtc *crtc)
+int i915gm_enable_vblank(struct drm_crtc *crtc)
{
struct drm_i915_private *dev_priv = to_i915(crtc->dev);
- if (dev_priv->i945gm_vblank.enabled++ == 0)
- schedule_work(&dev_priv->i945gm_vblank.work);
+ /*
+ * Vblank interrupts fail to wake the device up from C2+.
+ * Disabling render clock gating during C-states avoids
+ * the problem. There is a small power cost so we do this
+ * only when vblank interrupts are actually enabled.
+ */
+ if (dev_priv->vblank_enabled++ == 0)
+ I915_WRITE(SCPD0, _MASKED_BIT_ENABLE(CSTATE_RENDER_CLOCK_GATE_DISABLE));
return i8xx_enable_vblank(crtc);
}
@@ -2988,14 +2993,14 @@ void i8xx_disable_vblank(struct drm_crtc *crtc)
spin_unlock_irqrestore(&dev_priv->irq_lock, irqflags);
}
-void i945gm_disable_vblank(struct drm_crtc *crtc)
+void i915gm_disable_vblank(struct drm_crtc *crtc)
{
struct drm_i915_private *dev_priv = to_i915(crtc->dev);
i8xx_disable_vblank(crtc);
- if (--dev_priv->i945gm_vblank.enabled == 0)
- schedule_work(&dev_priv->i945gm_vblank.work);
+ if (--dev_priv->vblank_enabled == 0)
+ I915_WRITE(SCPD0, _MASKED_BIT_DISABLE(CSTATE_RENDER_CLOCK_GATE_DISABLE));
}
void i965_disable_vblank(struct drm_crtc *crtc)
@@ -3034,60 +3039,6 @@ void bdw_disable_vblank(struct drm_crtc *crtc)
spin_unlock_irqrestore(&dev_priv->irq_lock, irqflags);
}
-static void i945gm_vblank_work_func(struct work_struct *work)
-{
- struct drm_i915_private *dev_priv =
- container_of(work, struct drm_i915_private, i945gm_vblank.work);
-
- /*
- * Vblank interrupts fail to wake up the device from C3,
- * hence we want to prevent C3 usage while vblank interrupts
- * are enabled.
- */
- pm_qos_update_request(&dev_priv->i945gm_vblank.pm_qos,
- READ_ONCE(dev_priv->i945gm_vblank.enabled) ?
- dev_priv->i945gm_vblank.c3_disable_latency :
- PM_QOS_DEFAULT_VALUE);
-}
-
-static int cstate_disable_latency(const char *name)
-{
- const struct cpuidle_driver *drv;
- int i;
-
- drv = cpuidle_get_driver();
- if (!drv)
- return 0;
-
- for (i = 0; i < drv->state_count; i++) {
- const struct cpuidle_state *state = &drv->states[i];
-
- if (!strcmp(state->name, name))
- return state->exit_latency ?
- state->exit_latency - 1 : 0;
- }
-
- return 0;
-}
-
-static void i945gm_vblank_work_init(struct drm_i915_private *dev_priv)
-{
- INIT_WORK(&dev_priv->i945gm_vblank.work,
- i945gm_vblank_work_func);
-
- dev_priv->i945gm_vblank.c3_disable_latency =
- cstate_disable_latency("C3");
- pm_qos_add_request(&dev_priv->i945gm_vblank.pm_qos,
- PM_QOS_CPU_DMA_LATENCY,
- PM_QOS_DEFAULT_VALUE);
-}
-
-static void i945gm_vblank_work_fini(struct drm_i915_private *dev_priv)
-{
- cancel_work_sync(&dev_priv->i945gm_vblank.work);
- pm_qos_remove_request(&dev_priv->i945gm_vblank.pm_qos);
-}
-
static void ibx_irq_reset(struct drm_i915_private *dev_priv)
{
struct intel_uncore *uncore = &dev_priv->uncore;
@@ -4298,9 +4249,6 @@ void intel_irq_init(struct drm_i915_private *dev_priv)
struct intel_rps *rps = &dev_priv->gt_pm.rps;
int i;
- if (IS_I945GM(dev_priv))
- i945gm_vblank_work_init(dev_priv);
-
intel_hpd_init_work(dev_priv);
INIT_WORK(&rps->work, gen6_pm_rps_work);
@@ -4388,9 +4336,6 @@ void intel_irq_fini(struct drm_i915_private *i915)
{
int i;
- if (IS_I945GM(i915))
- i945gm_vblank_work_fini(i915);
-
for (i = 0; i < MAX_L3_SLICES; ++i)
kfree(i915->l3_parity.remap_info[i]);
}
diff --git a/drivers/gpu/drm/i915/i915_irq.h b/drivers/gpu/drm/i915/i915_irq.h
index 8e7e6071777e..19a3bc019535 100644
--- a/drivers/gpu/drm/i915/i915_irq.h
+++ b/drivers/gpu/drm/i915/i915_irq.h
@@ -122,12 +122,12 @@ u32 i915_get_vblank_counter(struct drm_crtc *crtc);
u32 g4x_get_vblank_counter(struct drm_crtc *crtc);
int i8xx_enable_vblank(struct drm_crtc *crtc);
-int i945gm_enable_vblank(struct drm_crtc *crtc);
+int i915gm_enable_vblank(struct drm_crtc *crtc);
int i965_enable_vblank(struct drm_crtc *crtc);
int ilk_enable_vblank(struct drm_crtc *crtc);
int bdw_enable_vblank(struct drm_crtc *crtc);
void i8xx_disable_vblank(struct drm_crtc *crtc);
-void i945gm_disable_vblank(struct drm_crtc *crtc);
+void i915gm_disable_vblank(struct drm_crtc *crtc);
void i965_disable_vblank(struct drm_crtc *crtc);
void ilk_disable_vblank(struct drm_crtc *crtc);
void bdw_disable_vblank(struct drm_crtc *crtc);
diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
index eefd789b9a28..13dd1df0c853 100644
--- a/drivers/gpu/drm/i915/i915_reg.h
+++ b/drivers/gpu/drm/i915/i915_reg.h
@@ -2709,6 +2709,7 @@ static inline bool i915_mmio_reg_valid(i915_reg_t reg)
#define VLV_GU_CTL0 _MMIO(VLV_DISPLAY_BASE + 0x2030)
#define VLV_GU_CTL1 _MMIO(VLV_DISPLAY_BASE + 0x2034)
#define SCPD0 _MMIO(0x209c) /* 915+ only */
+#define CSTATE_RENDER_CLOCK_GATE_DISABLE (1 << 5)
#define GEN2_IER _MMIO(0x20a0)
#define GEN2_IIR _MMIO(0x20a4)
#define GEN2_IMR _MMIO(0x20a8)
--
2.21.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply related [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
2019-10-03 14:02 [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround Ville Syrjala
@ 2019-10-03 14:12 ` Chris Wilson
2019-10-03 14:18 ` Ville Syrjälä
2019-10-03 16:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-04 1:24 ` ✗ Fi.CI.IGT: failure " Patchwork
2 siblings, 1 reply; 5+ messages in thread
From: Chris Wilson @ 2019-10-03 14:12 UTC (permalink / raw)
To: Ville Syrjala, intel-gfx
Quoting Ville Syrjala (2019-10-03 15:02:31)
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> The current "disable C3+" workaround for the delayed vblank
> irqs on i945gm no longer works. I'm not sure what changed, but
> now I need to also disable C2. I also got my hands on a i915gm
> machine that suffers from the same issue.
>
> After some furious poking of registers I managed to find a
> better workaround: The "Do not Turn off Core Render Clock in C
> states" bit. With that I no longer have to disable any C-states,
> and as a nice bonus the power cost is only ~1/4 of the
> "disable C3+" method (which mind you doesn't even work anymore,
> and so would have an even higher power cost if we made it work
> by also disabling C2).
>
> So let's throw out all the cpuidle/qos crap and just toggle
> the magic bit as needed. And we extend the workaround to cover
> i915gm as well.
Nice discovery. ScratchPad0 suggests that it may have been a late
addition, there might be some chips out there that don't have the magic
bit. Working on most is better than broken on all.
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Empirical results rule, and I for one am much happier without needing
qos dma_latency,
Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
2019-10-03 14:12 ` Chris Wilson
@ 2019-10-03 14:18 ` Ville Syrjälä
0 siblings, 0 replies; 5+ messages in thread
From: Ville Syrjälä @ 2019-10-03 14:18 UTC (permalink / raw)
To: Chris Wilson; +Cc: intel-gfx
On Thu, Oct 03, 2019 at 03:12:11PM +0100, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-10-03 15:02:31)
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > The current "disable C3+" workaround for the delayed vblank
> > irqs on i945gm no longer works. I'm not sure what changed, but
> > now I need to also disable C2. I also got my hands on a i915gm
> > machine that suffers from the same issue.
> >
> > After some furious poking of registers I managed to find a
> > better workaround: The "Do not Turn off Core Render Clock in C
> > states" bit. With that I no longer have to disable any C-states,
> > and as a nice bonus the power cost is only ~1/4 of the
> > "disable C3+" method (which mind you doesn't even work anymore,
> > and so would have an even higher power cost if we made it work
> > by also disabling C2).
> >
> > So let's throw out all the cpuidle/qos crap and just toggle
> > the magic bit as needed. And we extend the workaround to cover
> > i915gm as well.
>
> Nice discovery. ScratchPad0 suggests that it may have been a late
> addition, there might be some chips out there that don't have the magic
> bit. Working on most is better than broken on all.
Yeah. And at least 100% of *my* broken machines now work ;)
>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Empirical results rule, and I for one am much happier without needing
> qos dma_latency,
> Acked-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
2019-10-03 14:02 [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround Ville Syrjala
2019-10-03 14:12 ` Chris Wilson
@ 2019-10-03 16:39 ` Patchwork
2019-10-04 1:24 ` ✗ Fi.CI.IGT: failure " Patchwork
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2019-10-03 16:39 UTC (permalink / raw)
To: Ville Syrjälä; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
URL : https://patchwork.freedesktop.org/series/67541/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6998 -> Patchwork_14651
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/index.html
Known issues
------------
Here are the changes found in Patchwork_14651 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-skl-6600u: [PASS][1] -> [INCOMPLETE][2] ([fdo#107807])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/fi-skl-6600u/igt@i915_pm_rpm@module-reload.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/fi-skl-6600u/igt@i915_pm_rpm@module-reload.html
* igt@kms_frontbuffer_tracking@basic:
- fi-hsw-peppy: [PASS][3] -> [DMESG-WARN][4] ([fdo#102614])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/fi-hsw-peppy/igt@kms_frontbuffer_tracking@basic.html
#### Possible fixes ####
* igt@i915_selftest@live_execlists:
- fi-bsw-kefka: [DMESG-FAIL][5] ([fdo#111895]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/fi-bsw-kefka/igt@i915_selftest@live_execlists.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/fi-bsw-kefka/igt@i915_selftest@live_execlists.html
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-icl-u2: [FAIL][7] ([fdo#109483]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/fi-icl-u2/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#102614]: https://bugs.freedesktop.org/show_bug.cgi?id=102614
[fdo#107807]: https://bugs.freedesktop.org/show_bug.cgi?id=107807
[fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483
[fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735
[fdo#111895]: https://bugs.freedesktop.org/show_bug.cgi?id=111895
Participating hosts (51 -> 43)
------------------------------
Additional (1): fi-kbl-soraka
Missing (9): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-u3 fi-icl-y fi-blb-e6850 fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6998 -> Patchwork_14651
CI-20190529: 20190529
CI_DRM_6998: fd44976bff7ae3cdf72245ac33d92d2186e57e9b @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5210: 74f55119f9920b65996535210a09147997804136 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_14651: 7e3c560176a1e65252615e5128447d29e15c351a @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
7e3c560176a1 drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
* ✗ Fi.CI.IGT: failure for drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
2019-10-03 14:02 [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround Ville Syrjala
2019-10-03 14:12 ` Chris Wilson
2019-10-03 16:39 ` ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-10-04 1:24 ` Patchwork
2 siblings, 0 replies; 5+ messages in thread
From: Patchwork @ 2019-10-04 1:24 UTC (permalink / raw)
To: Ville Syrjala; +Cc: intel-gfx
== Series Details ==
Series: drm/i915: Implement a better i945gm vblank irq vs. C-states workaround
URL : https://patchwork.freedesktop.org/series/67541/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6998_full -> Patchwork_14651_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_14651_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_14651_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_14651_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_eio@in-flight-suspend:
- shard-iclb: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb7/igt@gem_eio@in-flight-suspend.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb4/igt@gem_eio@in-flight-suspend.html
* igt@gem_mmap_gtt@basic-small-copy:
- shard-hsw: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-hsw5/igt@gem_mmap_gtt@basic-small-copy.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-hsw6/igt@gem_mmap_gtt@basic-small-copy.html
* igt@i915_selftest@live_execlists:
- shard-iclb: [PASS][5] -> [DMESG-FAIL][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb8/igt@i915_selftest@live_execlists.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb1/igt@i915_selftest@live_execlists.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_exec_nop@basic-parallel:
- {shard-tglb}: [PASS][7] -> [INCOMPLETE][8] +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb4/igt@gem_exec_nop@basic-parallel.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb1/igt@gem_exec_nop@basic-parallel.html
Known issues
------------
Here are the changes found in Patchwork_14651_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@rcs0-s3:
- shard-iclb: [PASS][9] -> [DMESG-WARN][10] ([fdo#111764])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb7/igt@gem_ctx_isolation@rcs0-s3.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb4/igt@gem_ctx_isolation@rcs0-s3.html
* igt@gem_ctx_switch@vecs0-heavy-queue:
- shard-apl: [PASS][11] -> [INCOMPLETE][12] ([fdo#103927]) +2 similar issues
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-apl7/igt@gem_ctx_switch@vecs0-heavy-queue.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-apl4/igt@gem_ctx_switch@vecs0-heavy-queue.html
* igt@gem_exec_schedule@preemptive-hang-bsd:
- shard-iclb: [PASS][13] -> [SKIP][14] ([fdo#111325]) +9 similar issues
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb7/igt@gem_exec_schedule@preemptive-hang-bsd.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb4/igt@gem_exec_schedule@preemptive-hang-bsd.html
* igt@gem_exec_suspend@basic-s3:
- shard-skl: [PASS][15] -> [INCOMPLETE][16] ([fdo#104108])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-skl5/igt@gem_exec_suspend@basic-s3.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-skl5/igt@gem_exec_suspend@basic-s3.html
* igt@gem_mmap_gtt@hang:
- shard-apl: [PASS][17] -> [DMESG-WARN][18] ([fdo#109385])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-apl2/igt@gem_mmap_gtt@hang.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-apl2/igt@gem_mmap_gtt@hang.html
* igt@gem_userptr_blits@coherency-sync:
- shard-hsw: [PASS][19] -> [DMESG-WARN][20] ([fdo#111870]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-hsw2/igt@gem_userptr_blits@coherency-sync.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-hsw4/igt@gem_userptr_blits@coherency-sync.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
- shard-skl: [PASS][21] -> [DMESG-WARN][22] ([fdo#111870])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-skl7/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-skl2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
- shard-kbl: [PASS][23] -> [DMESG-WARN][24] ([fdo#111870])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-kbl4/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-kbl7/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-snb: [PASS][25] -> [DMESG-WARN][26] ([fdo#111870]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-snb1/igt@gem_userptr_blits@sync-unmap-cycles.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-snb4/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@kms_busy@basic-modeset-c:
- shard-hsw: [PASS][27] -> [INCOMPLETE][28] ([fdo#103540])
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-hsw6/igt@kms_busy@basic-modeset-c.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-hsw6/igt@kms_busy@basic-modeset-c.html
* igt@kms_flip@flip-vs-expired-vblank-interruptible:
- shard-skl: [PASS][29] -> [FAIL][30] ([fdo#105363])
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-skl10/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-skl4/igt@kms_flip@flip-vs-expired-vblank-interruptible.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-snb: [PASS][31] -> [DMESG-WARN][32] ([fdo#102365])
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-snb4/igt@kms_flip@flip-vs-suspend-interruptible.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-snb1/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt:
- shard-iclb: [PASS][33] -> [FAIL][34] ([fdo#103167]) +2 similar issues
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-draw-blt.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes:
- shard-apl: [PASS][35] -> [DMESG-WARN][36] ([fdo#108566]) +3 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-apl2/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-apl8/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-b-planes.html
* igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min:
- shard-skl: [PASS][37] -> [FAIL][38] ([fdo#108145])
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-skl1/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-skl6/igt@kms_plane_alpha_blend@pipe-b-constant-alpha-min.html
* igt@kms_plane_lowres@pipe-a-tiling-y:
- shard-iclb: [PASS][39] -> [FAIL][40] ([fdo#103166])
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb2/igt@kms_plane_lowres@pipe-a-tiling-y.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb8/igt@kms_plane_lowres@pipe-a-tiling-y.html
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [PASS][41] -> [SKIP][42] ([fdo#109642] / [fdo#111068])
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb2/igt@kms_psr2_su@frontbuffer.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb8/igt@kms_psr2_su@frontbuffer.html
* igt@kms_psr@primary_render:
- shard-iclb: [PASS][43] -> [INCOMPLETE][44] ([fdo#107713])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb6/igt@kms_psr@primary_render.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb7/igt@kms_psr@primary_render.html
* igt@kms_psr@psr2_dpms:
- shard-iclb: [PASS][45] -> [SKIP][46] ([fdo#109441]) +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb2/igt@kms_psr@psr2_dpms.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb8/igt@kms_psr@psr2_dpms.html
* igt@prime_busy@hang-bsd2:
- shard-iclb: [PASS][47] -> [SKIP][48] ([fdo#109276]) +27 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb2/igt@prime_busy@hang-bsd2.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb8/igt@prime_busy@hang-bsd2.html
#### Possible fixes ####
* igt@gem_ctx_shared@q-smoketest-render:
- {shard-tglb}: [INCOMPLETE][49] ([fdo# 111852 ]) -> [PASS][50]
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb3/igt@gem_ctx_shared@q-smoketest-render.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb5/igt@gem_ctx_shared@q-smoketest-render.html
* igt@gem_eio@reset-stress:
- shard-snb: [FAIL][51] ([fdo#109661]) -> [PASS][52]
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-snb2/igt@gem_eio@reset-stress.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-snb5/igt@gem_eio@reset-stress.html
* igt@gem_exec_async@concurrent-writes-bsd:
- shard-iclb: [SKIP][53] ([fdo#111325]) -> [PASS][54] +2 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb1/igt@gem_exec_async@concurrent-writes-bsd.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb5/igt@gem_exec_async@concurrent-writes-bsd.html
* igt@gem_exec_reuse@single:
- shard-snb: [INCOMPLETE][55] ([fdo#105411]) -> [PASS][56]
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-snb1/igt@gem_exec_reuse@single.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-snb4/igt@gem_exec_reuse@single.html
* igt@gem_exec_schedule@preempt-contexts-bsd2:
- shard-iclb: [SKIP][57] ([fdo#109276]) -> [PASS][58] +19 similar issues
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb7/igt@gem_exec_schedule@preempt-contexts-bsd2.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb4/igt@gem_exec_schedule@preempt-contexts-bsd2.html
* igt@gem_mmap_gtt@basic-small-copy:
- shard-snb: [DMESG-WARN][59] ([fdo#111891]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-snb1/igt@gem_mmap_gtt@basic-small-copy.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-snb4/igt@gem_mmap_gtt@basic-small-copy.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-kbl: [DMESG-WARN][61] ([fdo#111870]) -> [PASS][62]
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-kbl7/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-kbl2/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
- shard-skl: [DMESG-WARN][63] ([fdo#111870]) -> [PASS][64]
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-skl1/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-skl9/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-glk: [DMESG-WARN][65] ([fdo#111870]) -> [PASS][66]
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-glk3/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-glk5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
- shard-hsw: [DMESG-WARN][67] ([fdo#111870]) -> [PASS][68]
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-hsw1/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-hsw7/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
* igt@gem_userptr_blits@sync-unmap:
- shard-snb: [DMESG-WARN][69] ([fdo#111870]) -> [PASS][70]
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-snb5/igt@gem_userptr_blits@sync-unmap.html
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-snb7/igt@gem_userptr_blits@sync-unmap.html
* igt@kms_color@pipe-a-gamma:
- {shard-tglb}: [FAIL][71] ([fdo#104782]) -> [PASS][72]
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb1/igt@kms_color@pipe-a-gamma.html
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb7/igt@kms_color@pipe-a-gamma.html
* igt@kms_flip@flip-vs-suspend:
- {shard-tglb}: [INCOMPLETE][73] ([fdo#111714]) -> [PASS][74]
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb8/igt@kms_flip@flip-vs-suspend.html
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb6/igt@kms_flip@flip-vs-suspend.html
* igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render:
- shard-iclb: [FAIL][75] ([fdo#103167]) -> [PASS][76] +7 similar issues
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-apl: [DMESG-WARN][77] ([fdo#108566]) -> [PASS][78] +3 similar issues
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-apl6/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move:
- {shard-tglb}: [FAIL][79] ([fdo#103167]) -> [PASS][80] +9 similar issues
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb1/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-cur-indfb-move.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes:
- {shard-tglb}: [INCOMPLETE][81] ([fdo#111832]) -> [PASS][82] +1 similar issue
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb5/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes.html
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb6/igt@kms_plane@plane-panning-bottom-right-suspend-pipe-a-planes.html
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [FAIL][83] ([fdo#108145] / [fdo#110403]) -> [PASS][84]
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-skl6/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-skl8/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html
* igt@kms_plane_alpha_blend@pipe-c-coverage-vs-premult-vs-constant:
- {shard-tglb}: [INCOMPLETE][85] -> [PASS][86]
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-tglb1/igt@kms_plane_alpha_blend@pipe-c-coverage-vs-premult-vs-constant.html
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-tglb5/igt@kms_plane_alpha_blend@pipe-c-coverage-vs-premult-vs-constant.html
* igt@kms_psr@psr2_primary_mmap_gtt:
- shard-iclb: [SKIP][87] ([fdo#109441]) -> [PASS][88] +1 similar issue
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb8/igt@kms_psr@psr2_primary_mmap_gtt.html
[88]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb2/igt@kms_psr@psr2_primary_mmap_gtt.html
#### Warnings ####
* igt@gem_mocs_settings@mocs-rc6-bsd2:
- shard-iclb: [FAIL][89] ([fdo#111330]) -> [SKIP][90] ([fdo#109276])
[89]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6998/shard-iclb1/igt@gem_mocs_settings@mocs-rc6-bsd2.html
[90]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/shard-iclb7/igt@gem_mocs_settings@mocs-rc6-bsd2.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo# 111852 ]: https://bugs.freedesktop.org/show_bug.cgi?id= 111852
[fdo#102365]: https://bugs.freedesktop.org/show_bug.cgi?id=102365
[fdo#103166]: https://bugs.freedesktop.org/show_bug.cgi?id=103166
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#104108]: https://bugs.freedesktop.org/show_bug.cgi?id=104108
[fdo#104782]: https://bugs.freedesktop.org/show_bug.cgi?id=104782
[fdo#105363]: https://bugs.freedesktop.org/show_bug.cgi?id=105363
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#109661]: https://bugs.freedesktop.org/show_bug.cgi?id=109661
[fdo#110403]: https://bugs.freedesktop.org/show_bug.cgi?id=110403
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600
[fdo#111646]: https://bugs.freedesktop.org/show_bug.cgi?id=111646
[fdo#111671]: https://bugs.freedesktop.org/show_bug.cgi?id=111671
[fdo#111714]: https://bugs.freedesktop.org/show_bug.cgi?id=111714
[fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735
[fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764
[fdo#111795 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111795
[fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832
[fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850
[fdo#111855]: https://bugs.freedesktop.org/show_bug.cgi?id=111855
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#111891]: https://bugs.freedesktop.org/show_bug.cgi?id=111891
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* CI: CI-20190529 -> None
* Linux: CI_DRM_6998 -> Patchwork_14651
CI-20190529: 20190
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_14651/index.html
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2019-10-04 1:24 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-03 14:02 [PATCH] drm/i915: Implement a better i945gm vblank irq vs. C-states workaround Ville Syrjala
2019-10-03 14:12 ` Chris Wilson
2019-10-03 14:18 ` Ville Syrjälä
2019-10-03 16:39 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-10-04 1:24 ` ✗ Fi.CI.IGT: failure " Patchwork
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.