* [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 16:10 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-11-28 16:10 UTC (permalink / raw) To: Intel-gfx From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> We used to report the minimum possible frequency as both requested and active while GPU was in sleep state. This was a consequence of sampling the value from the "current frequency" field in our software tracking. This was strictly speaking wrong, but given that until recently the current frequency in sleeping state used to be equal to minimum, it did not stand out sufficiently to be noticed as such. After some recent changes have made the current frequency be reported as last active before GPU went to sleep, meaning both requested and active frequencies could end up being reported at their maximum values for the duration of the GPU idle state, it became much more obvious that this does not make sense. To fix this we will now sample the frequency counters only when the GPU is awake. As a consequence reported frequencies could be reported as below the GPU reported minimum but that should be much less confusing that the current situation. Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> --- drivers/gpu/drm/i915/i915_pmu.c | 44 +++++++++++++++++---------------- 1 file changed, 23 insertions(+), 21 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c index 95e824a78d4d..b576a2be9f81 100644 --- a/drivers/gpu/drm/i915/i915_pmu.c +++ b/drivers/gpu/drm/i915/i915_pmu.c @@ -378,32 +378,32 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) struct i915_pmu *pmu = &i915->pmu; struct intel_rps *rps = >->rps; + if (!(pmu->enable & + (config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY) | + config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY))) || + !intel_gt_pm_get_if_awake(gt)) + return; + if (pmu->enable & config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY)) { u32 val; - val = rps->cur_freq; - if (intel_gt_pm_get_if_awake(gt)) { - u32 stat; - - /* - * We take a quick peek here without using forcewake - * so that we don't perturb the system under observation - * (forcewake => !rc6 => increased power use). We expect - * that if the read fails because it is outside of the - * mmio power well, then it will return 0 -- in which - * case we assume the system is running at the intended - * frequency. Fortunately, the read should rarely fail! - */ - stat = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); - if (stat) - val = intel_get_cagf(rps, stat); - - intel_gt_pm_put_async(gt); - } + /* + * We take a quick peek here without using forcewake + * so that we don't perturb the system under observation + * (forcewake => !rc6 => increased power use). We expect + * that if the read fails because it is outside of the + * mmio power well, then it will return 0 -- in which + * case we assume the system is running at the intended + * frequency. Fortunately, the read should rarely fail! + */ + val = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); + if (val) + val = intel_get_cagf(rps, val); + else + val = rps->cur_freq; add_sample_mult(&pmu->sample[__I915_SAMPLE_FREQ_ACT], - intel_gpu_freq(rps, val), - period_ns / 1000); + intel_gpu_freq(rps, val), period_ns / 1000); } if (pmu->enable & config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY)) { @@ -411,6 +411,8 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) intel_gpu_freq(rps, rps->cur_freq), period_ns / 1000); } + + intel_gt_pm_put_async(gt); } static enum hrtimer_restart i915_sample(struct hrtimer *hrtimer) -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 19+ messages in thread
* [Intel-gfx] [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 16:10 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-11-28 16:10 UTC (permalink / raw) To: Intel-gfx From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> We used to report the minimum possible frequency as both requested and active while GPU was in sleep state. This was a consequence of sampling the value from the "current frequency" field in our software tracking. This was strictly speaking wrong, but given that until recently the current frequency in sleeping state used to be equal to minimum, it did not stand out sufficiently to be noticed as such. After some recent changes have made the current frequency be reported as last active before GPU went to sleep, meaning both requested and active frequencies could end up being reported at their maximum values for the duration of the GPU idle state, it became much more obvious that this does not make sense. To fix this we will now sample the frequency counters only when the GPU is awake. As a consequence reported frequencies could be reported as below the GPU reported minimum but that should be much less confusing that the current situation. Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> --- drivers/gpu/drm/i915/i915_pmu.c | 44 +++++++++++++++++---------------- 1 file changed, 23 insertions(+), 21 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c index 95e824a78d4d..b576a2be9f81 100644 --- a/drivers/gpu/drm/i915/i915_pmu.c +++ b/drivers/gpu/drm/i915/i915_pmu.c @@ -378,32 +378,32 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) struct i915_pmu *pmu = &i915->pmu; struct intel_rps *rps = >->rps; + if (!(pmu->enable & + (config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY) | + config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY))) || + !intel_gt_pm_get_if_awake(gt)) + return; + if (pmu->enable & config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY)) { u32 val; - val = rps->cur_freq; - if (intel_gt_pm_get_if_awake(gt)) { - u32 stat; - - /* - * We take a quick peek here without using forcewake - * so that we don't perturb the system under observation - * (forcewake => !rc6 => increased power use). We expect - * that if the read fails because it is outside of the - * mmio power well, then it will return 0 -- in which - * case we assume the system is running at the intended - * frequency. Fortunately, the read should rarely fail! - */ - stat = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); - if (stat) - val = intel_get_cagf(rps, stat); - - intel_gt_pm_put_async(gt); - } + /* + * We take a quick peek here without using forcewake + * so that we don't perturb the system under observation + * (forcewake => !rc6 => increased power use). We expect + * that if the read fails because it is outside of the + * mmio power well, then it will return 0 -- in which + * case we assume the system is running at the intended + * frequency. Fortunately, the read should rarely fail! + */ + val = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); + if (val) + val = intel_get_cagf(rps, val); + else + val = rps->cur_freq; add_sample_mult(&pmu->sample[__I915_SAMPLE_FREQ_ACT], - intel_gpu_freq(rps, val), - period_ns / 1000); + intel_gpu_freq(rps, val), period_ns / 1000); } if (pmu->enable & config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY)) { @@ -411,6 +411,8 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) intel_gpu_freq(rps, rps->cur_freq), period_ns / 1000); } + + intel_gt_pm_put_async(gt); } static enum hrtimer_restart i915_sample(struct hrtimer *hrtimer) -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 19+ messages in thread
* Re: [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 16:19 ` Chris Wilson 0 siblings, 0 replies; 19+ messages in thread From: Chris Wilson @ 2019-11-28 16:19 UTC (permalink / raw) To: Intel-gfx, Tvrtko Ursulin Quoting Tvrtko Ursulin (2019-11-28 16:10:51) > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > We used to report the minimum possible frequency as both requested and > active while GPU was in sleep state. This was a consequence of sampling > the value from the "current frequency" field in our software tracking. > > This was strictly speaking wrong, but given that until recently the > current frequency in sleeping state used to be equal to minimum, it did > not stand out sufficiently to be noticed as such. > > After some recent changes have made the current frequency be reported > as last active before GPU went to sleep, meaning both requested and active > frequencies could end up being reported at their maximum values for the > duration of the GPU idle state, it became much more obvious that this does > not make sense. > > To fix this we will now sample the frequency counters only when the GPU is > awake. As a consequence reported frequencies could be reported as below > the GPU reported minimum but that should be much less confusing that the > current situation. > > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Hmm. 0/0 while off, that will be a bit of a shock. Idea/codewise Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> I'll dogfood it a bit to see how much getting used to it will take :) > --- > drivers/gpu/drm/i915/i915_pmu.c | 44 +++++++++++++++++---------------- > 1 file changed, 23 insertions(+), 21 deletions(-) > > diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c > index 95e824a78d4d..b576a2be9f81 100644 > --- a/drivers/gpu/drm/i915/i915_pmu.c > +++ b/drivers/gpu/drm/i915/i915_pmu.c > @@ -378,32 +378,32 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) > struct i915_pmu *pmu = &i915->pmu; > struct intel_rps *rps = >->rps; > > + if (!(pmu->enable & > + (config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY) | > + config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY))) || > + !intel_gt_pm_get_if_awake(gt)) > + return; Fwiw, I'd put this as two if()s since the multiline flags makes it harder to read. Any chance we could do a if (!frequency_sample_enabled(pmu)) return; /* Report 0/0 (actual/requested) frequency while parked */ if (!intel_gt_pm_get_if_awake(gt)) return; -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 16:19 ` Chris Wilson 0 siblings, 0 replies; 19+ messages in thread From: Chris Wilson @ 2019-11-28 16:19 UTC (permalink / raw) To: Intel-gfx, Tvrtko Ursulin Quoting Tvrtko Ursulin (2019-11-28 16:10:51) > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > We used to report the minimum possible frequency as both requested and > active while GPU was in sleep state. This was a consequence of sampling > the value from the "current frequency" field in our software tracking. > > This was strictly speaking wrong, but given that until recently the > current frequency in sleeping state used to be equal to minimum, it did > not stand out sufficiently to be noticed as such. > > After some recent changes have made the current frequency be reported > as last active before GPU went to sleep, meaning both requested and active > frequencies could end up being reported at their maximum values for the > duration of the GPU idle state, it became much more obvious that this does > not make sense. > > To fix this we will now sample the frequency counters only when the GPU is > awake. As a consequence reported frequencies could be reported as below > the GPU reported minimum but that should be much less confusing that the > current situation. > > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Hmm. 0/0 while off, that will be a bit of a shock. Idea/codewise Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> I'll dogfood it a bit to see how much getting used to it will take :) > --- > drivers/gpu/drm/i915/i915_pmu.c | 44 +++++++++++++++++---------------- > 1 file changed, 23 insertions(+), 21 deletions(-) > > diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c > index 95e824a78d4d..b576a2be9f81 100644 > --- a/drivers/gpu/drm/i915/i915_pmu.c > +++ b/drivers/gpu/drm/i915/i915_pmu.c > @@ -378,32 +378,32 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) > struct i915_pmu *pmu = &i915->pmu; > struct intel_rps *rps = >->rps; > > + if (!(pmu->enable & > + (config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY) | > + config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY))) || > + !intel_gt_pm_get_if_awake(gt)) > + return; Fwiw, I'd put this as two if()s since the multiline flags makes it harder to read. Any chance we could do a if (!frequency_sample_enabled(pmu)) return; /* Report 0/0 (actual/requested) frequency while parked */ if (!intel_gt_pm_get_if_awake(gt)) return; -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 16:22 ` Chris Wilson 0 siblings, 0 replies; 19+ messages in thread From: Chris Wilson @ 2019-11-28 16:22 UTC (permalink / raw) To: Intel-gfx, Tvrtko Ursulin Quoting Chris Wilson (2019-11-28 16:19:49) > Quoting Tvrtko Ursulin (2019-11-28 16:10:51) > > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > > > We used to report the minimum possible frequency as both requested and > > active while GPU was in sleep state. This was a consequence of sampling > > the value from the "current frequency" field in our software tracking. > > > > This was strictly speaking wrong, but given that until recently the > > current frequency in sleeping state used to be equal to minimum, it did > > not stand out sufficiently to be noticed as such. > > > > After some recent changes have made the current frequency be reported > > as last active before GPU went to sleep, meaning both requested and active > > frequencies could end up being reported at their maximum values for the > > duration of the GPU idle state, it became much more obvious that this does > > not make sense. > > > > To fix this we will now sample the frequency counters only when the GPU is > > awake. As a consequence reported frequencies could be reported as below > > the GPU reported minimum but that should be much less confusing that the > > current situation. > > > > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > Hmm. 0/0 while off, that will be a bit of a shock. There is a consistency question of whether we should do the same through the [second class ;] sysfs/ interface. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 16:22 ` Chris Wilson 0 siblings, 0 replies; 19+ messages in thread From: Chris Wilson @ 2019-11-28 16:22 UTC (permalink / raw) To: Intel-gfx, Tvrtko Ursulin Quoting Chris Wilson (2019-11-28 16:19:49) > Quoting Tvrtko Ursulin (2019-11-28 16:10:51) > > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > > > We used to report the minimum possible frequency as both requested and > > active while GPU was in sleep state. This was a consequence of sampling > > the value from the "current frequency" field in our software tracking. > > > > This was strictly speaking wrong, but given that until recently the > > current frequency in sleeping state used to be equal to minimum, it did > > not stand out sufficiently to be noticed as such. > > > > After some recent changes have made the current frequency be reported > > as last active before GPU went to sleep, meaning both requested and active > > frequencies could end up being reported at their maximum values for the > > duration of the GPU idle state, it became much more obvious that this does > > not make sense. > > > > To fix this we will now sample the frequency counters only when the GPU is > > awake. As a consequence reported frequencies could be reported as below > > the GPU reported minimum but that should be much less confusing that the > > current situation. > > > > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > Hmm. 0/0 while off, that will be a bit of a shock. There is a consistency question of whether we should do the same through the [second class ;] sysfs/ interface. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 17:23 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-11-28 17:23 UTC (permalink / raw) To: Chris Wilson, Intel-gfx On 28/11/2019 16:22, Chris Wilson wrote: > Quoting Chris Wilson (2019-11-28 16:19:49) >> Quoting Tvrtko Ursulin (2019-11-28 16:10:51) >>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >>> >>> We used to report the minimum possible frequency as both requested and >>> active while GPU was in sleep state. This was a consequence of sampling >>> the value from the "current frequency" field in our software tracking. >>> >>> This was strictly speaking wrong, but given that until recently the >>> current frequency in sleeping state used to be equal to minimum, it did >>> not stand out sufficiently to be noticed as such. >>> >>> After some recent changes have made the current frequency be reported >>> as last active before GPU went to sleep, meaning both requested and active >>> frequencies could end up being reported at their maximum values for the >>> duration of the GPU idle state, it became much more obvious that this does >>> not make sense. >>> >>> To fix this we will now sample the frequency counters only when the GPU is >>> awake. As a consequence reported frequencies could be reported as below >>> the GPU reported minimum but that should be much less confusing that the >>> current situation. >>> >>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >> >> Hmm. 0/0 while off, that will be a bit of a shock. > > There is a consistency question of whether we should do the same through > the [second class ;] sysfs/ interface. I am not sure cur_freq even belongs in sysfs. But IGT/i915_pm_rps seems to be depending on the current semantics. Act_freq on the other hand is always reading the hw register. So should probably stay like that. Since it is in sysfs so ABI. Where this leaves the PMU I don't know. Regards, Tvrtko _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 17:23 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-11-28 17:23 UTC (permalink / raw) To: Chris Wilson, Intel-gfx On 28/11/2019 16:22, Chris Wilson wrote: > Quoting Chris Wilson (2019-11-28 16:19:49) >> Quoting Tvrtko Ursulin (2019-11-28 16:10:51) >>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >>> >>> We used to report the minimum possible frequency as both requested and >>> active while GPU was in sleep state. This was a consequence of sampling >>> the value from the "current frequency" field in our software tracking. >>> >>> This was strictly speaking wrong, but given that until recently the >>> current frequency in sleeping state used to be equal to minimum, it did >>> not stand out sufficiently to be noticed as such. >>> >>> After some recent changes have made the current frequency be reported >>> as last active before GPU went to sleep, meaning both requested and active >>> frequencies could end up being reported at their maximum values for the >>> duration of the GPU idle state, it became much more obvious that this does >>> not make sense. >>> >>> To fix this we will now sample the frequency counters only when the GPU is >>> awake. As a consequence reported frequencies could be reported as below >>> the GPU reported minimum but that should be much less confusing that the >>> current situation. >>> >>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >> >> Hmm. 0/0 while off, that will be a bit of a shock. > > There is a consistency question of whether we should do the same through > the [second class ;] sysfs/ interface. I am not sure cur_freq even belongs in sysfs. But IGT/i915_pm_rps seems to be depending on the current semantics. Act_freq on the other hand is always reading the hw register. So should probably stay like that. Since it is in sysfs so ABI. Where this leaves the PMU I don't know. Regards, Tvrtko _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* [PATCH v2] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-29 10:54 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-11-29 10:54 UTC (permalink / raw) To: Intel-gfx From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> We used to report the minimum possible frequency as both requested and active while GPU was in sleep state. This was a consequence of sampling the value from the "current frequency" field in our software tracking. This was strictly speaking wrong, but given that until recently the current frequency in sleeping state used to be equal to minimum, it did not stand out sufficiently to be noticed as such. After some recent changes have made the current frequency be reported as last active before GPU went to sleep, meaning both requested and active frequencies could end up being reported at their maximum values for the duration of the GPU idle state, it became much more obvious that this does not make sense. To fix this we will now sample the frequency counters only when the GPU is awake. As a consequence reported frequencies could be reported as below the GPU reported minimum but that should be much less confusing that the current situation. v2: * Split out early exit conditions for readability. (Chris) Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> --- drivers/gpu/drm/i915/i915_pmu.c | 52 ++++++++++++++++++++------------- 1 file changed, 31 insertions(+), 21 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c index 95e824a78d4d..eaad9c97d031 100644 --- a/drivers/gpu/drm/i915/i915_pmu.c +++ b/drivers/gpu/drm/i915/i915_pmu.c @@ -370,6 +370,13 @@ add_sample_mult(struct i915_pmu_sample *sample, u32 val, u32 mul) sample->cur += mul_u32_u32(val, mul); } +static bool frequency_sampling_enabled(struct i915_pmu *pmu) +{ + return pmu->enable & + (config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY) | + config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY)); +} + static void frequency_sample(struct intel_gt *gt, unsigned int period_ns) { @@ -378,32 +385,33 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) struct i915_pmu *pmu = &i915->pmu; struct intel_rps *rps = >->rps; + if (!frequency_sampling_enabled(pmu)) + return; + + /* Report 0/0 (actual/requested) frequency while parked. */ + if (!intel_gt_pm_get_if_awake(gt)) + return; + if (pmu->enable & config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY)) { u32 val; - val = rps->cur_freq; - if (intel_gt_pm_get_if_awake(gt)) { - u32 stat; - - /* - * We take a quick peek here without using forcewake - * so that we don't perturb the system under observation - * (forcewake => !rc6 => increased power use). We expect - * that if the read fails because it is outside of the - * mmio power well, then it will return 0 -- in which - * case we assume the system is running at the intended - * frequency. Fortunately, the read should rarely fail! - */ - stat = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); - if (stat) - val = intel_get_cagf(rps, stat); - - intel_gt_pm_put_async(gt); - } + /* + * We take a quick peek here without using forcewake + * so that we don't perturb the system under observation + * (forcewake => !rc6 => increased power use). We expect + * that if the read fails because it is outside of the + * mmio power well, then it will return 0 -- in which + * case we assume the system is running at the intended + * frequency. Fortunately, the read should rarely fail! + */ + val = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); + if (val) + val = intel_get_cagf(rps, val); + else + val = rps->cur_freq; add_sample_mult(&pmu->sample[__I915_SAMPLE_FREQ_ACT], - intel_gpu_freq(rps, val), - period_ns / 1000); + intel_gpu_freq(rps, val), period_ns / 1000); } if (pmu->enable & config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY)) { @@ -411,6 +419,8 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) intel_gpu_freq(rps, rps->cur_freq), period_ns / 1000); } + + intel_gt_pm_put_async(gt); } static enum hrtimer_restart i915_sample(struct hrtimer *hrtimer) -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 19+ messages in thread
* [Intel-gfx] [PATCH v2] drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-29 10:54 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-11-29 10:54 UTC (permalink / raw) To: Intel-gfx From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> We used to report the minimum possible frequency as both requested and active while GPU was in sleep state. This was a consequence of sampling the value from the "current frequency" field in our software tracking. This was strictly speaking wrong, but given that until recently the current frequency in sleeping state used to be equal to minimum, it did not stand out sufficiently to be noticed as such. After some recent changes have made the current frequency be reported as last active before GPU went to sleep, meaning both requested and active frequencies could end up being reported at their maximum values for the duration of the GPU idle state, it became much more obvious that this does not make sense. To fix this we will now sample the frequency counters only when the GPU is awake. As a consequence reported frequencies could be reported as below the GPU reported minimum but that should be much less confusing that the current situation. v2: * Split out early exit conditions for readability. (Chris) Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> --- drivers/gpu/drm/i915/i915_pmu.c | 52 ++++++++++++++++++++------------- 1 file changed, 31 insertions(+), 21 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_pmu.c b/drivers/gpu/drm/i915/i915_pmu.c index 95e824a78d4d..eaad9c97d031 100644 --- a/drivers/gpu/drm/i915/i915_pmu.c +++ b/drivers/gpu/drm/i915/i915_pmu.c @@ -370,6 +370,13 @@ add_sample_mult(struct i915_pmu_sample *sample, u32 val, u32 mul) sample->cur += mul_u32_u32(val, mul); } +static bool frequency_sampling_enabled(struct i915_pmu *pmu) +{ + return pmu->enable & + (config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY) | + config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY)); +} + static void frequency_sample(struct intel_gt *gt, unsigned int period_ns) { @@ -378,32 +385,33 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) struct i915_pmu *pmu = &i915->pmu; struct intel_rps *rps = >->rps; + if (!frequency_sampling_enabled(pmu)) + return; + + /* Report 0/0 (actual/requested) frequency while parked. */ + if (!intel_gt_pm_get_if_awake(gt)) + return; + if (pmu->enable & config_enabled_mask(I915_PMU_ACTUAL_FREQUENCY)) { u32 val; - val = rps->cur_freq; - if (intel_gt_pm_get_if_awake(gt)) { - u32 stat; - - /* - * We take a quick peek here without using forcewake - * so that we don't perturb the system under observation - * (forcewake => !rc6 => increased power use). We expect - * that if the read fails because it is outside of the - * mmio power well, then it will return 0 -- in which - * case we assume the system is running at the intended - * frequency. Fortunately, the read should rarely fail! - */ - stat = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); - if (stat) - val = intel_get_cagf(rps, stat); - - intel_gt_pm_put_async(gt); - } + /* + * We take a quick peek here without using forcewake + * so that we don't perturb the system under observation + * (forcewake => !rc6 => increased power use). We expect + * that if the read fails because it is outside of the + * mmio power well, then it will return 0 -- in which + * case we assume the system is running at the intended + * frequency. Fortunately, the read should rarely fail! + */ + val = intel_uncore_read_fw(uncore, GEN6_RPSTAT1); + if (val) + val = intel_get_cagf(rps, val); + else + val = rps->cur_freq; add_sample_mult(&pmu->sample[__I915_SAMPLE_FREQ_ACT], - intel_gpu_freq(rps, val), - period_ns / 1000); + intel_gpu_freq(rps, val), period_ns / 1000); } if (pmu->enable & config_enabled_mask(I915_PMU_REQUESTED_FREQUENCY)) { @@ -411,6 +419,8 @@ frequency_sample(struct intel_gt *gt, unsigned int period_ns) intel_gpu_freq(rps, rps->cur_freq), period_ns / 1000); } + + intel_gt_pm_put_async(gt); } static enum hrtimer_restart i915_sample(struct hrtimer *hrtimer) -- 2.20.1 _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply related [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/pmu: Report frequency as zero while GPU is sleeping 2019-11-29 10:54 ` [Intel-gfx] " Tvrtko Ursulin (?) @ 2019-12-06 12:32 ` Chris Wilson 2019-12-06 13:04 ` Tvrtko Ursulin -1 siblings, 1 reply; 19+ messages in thread From: Chris Wilson @ 2019-12-06 12:32 UTC (permalink / raw) To: Intel-gfx, Tvrtko Ursulin Quoting Tvrtko Ursulin (2019-11-29 10:54:36) > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > We used to report the minimum possible frequency as both requested and > active while GPU was in sleep state. This was a consequence of sampling > the value from the "current frequency" field in our software tracking. > > This was strictly speaking wrong, but given that until recently the > current frequency in sleeping state used to be equal to minimum, it did > not stand out sufficiently to be noticed as such. > > After some recent changes have made the current frequency be reported > as last active before GPU went to sleep, meaning both requested and active > frequencies could end up being reported at their maximum values for the > duration of the GPU idle state, it became much more obvious that this does > not make sense. > > To fix this we will now sample the frequency counters only when the GPU is > awake. As a consequence reported frequencies could be reported as below > the GPU reported minimum but that should be much less confusing that the > current situation. > > v2: > * Split out early exit conditions for readability. (Chris) > > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> I'm happy if you are happy... -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/pmu: Report frequency as zero while GPU is sleeping 2019-12-06 12:32 ` Chris Wilson @ 2019-12-06 13:04 ` Tvrtko Ursulin 0 siblings, 0 replies; 19+ messages in thread From: Tvrtko Ursulin @ 2019-12-06 13:04 UTC (permalink / raw) To: Chris Wilson, Intel-gfx On 06/12/2019 12:32, Chris Wilson wrote: > Quoting Tvrtko Ursulin (2019-11-29 10:54:36) >> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >> >> We used to report the minimum possible frequency as both requested and >> active while GPU was in sleep state. This was a consequence of sampling >> the value from the "current frequency" field in our software tracking. >> >> This was strictly speaking wrong, but given that until recently the >> current frequency in sleeping state used to be equal to minimum, it did >> not stand out sufficiently to be noticed as such. >> >> After some recent changes have made the current frequency be reported >> as last active before GPU went to sleep, meaning both requested and active >> frequencies could end up being reported at their maximum values for the >> duration of the GPU idle state, it became much more obvious that this does >> not make sense. >> >> To fix this we will now sample the frequency counters only when the GPU is >> awake. As a consequence reported frequencies could be reported as below >> the GPU reported minimum but that should be much less confusing that the >> current situation. >> >> v2: >> * Split out early exit conditions for readability. (Chris) >> >> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> >> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> > > I'm happy if you are happy... Okay pushed, thanks! Regards, Tvrtko _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* Re: [Intel-gfx] [PATCH v2] drm/i915/pmu: Report frequency as zero while GPU is sleeping 2019-11-29 10:54 ` [Intel-gfx] " Tvrtko Ursulin (?) (?) @ 2019-12-06 12:33 ` Chris Wilson -1 siblings, 0 replies; 19+ messages in thread From: Chris Wilson @ 2019-12-06 12:33 UTC (permalink / raw) To: Intel-gfx, Tvrtko Ursulin Quoting Tvrtko Ursulin (2019-11-29 10:54:36) > From: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > > We used to report the minimum possible frequency as both requested and > active while GPU was in sleep state. This was a consequence of sampling > the value from the "current frequency" field in our software tracking. > > This was strictly speaking wrong, but given that until recently the > current frequency in sleeping state used to be equal to minimum, it did > not stand out sufficiently to be noticed as such. > > After some recent changes have made the current frequency be reported > as last active before GPU went to sleep, meaning both requested and active > frequencies could end up being reported at their maximum values for the > duration of the GPU idle state, it became much more obvious that this does > not make sense. > > To fix this we will now sample the frequency counters only when the GPU is > awake. As a consequence reported frequencies could be reported as below > the GPU reported minimum but that should be much less confusing that the > current situation. > > v2: > * Split out early exit conditions for readability. (Chris) > Closes: https://gitlab.freedesktop.org/drm/intel/issues/675 > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Reviewed-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] 19+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 19:26 ` Patchwork 0 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2019-11-28 19:26 UTC (permalink / raw) To: Tvrtko Ursulin; +Cc: intel-gfx == Series Details == Series: drm/i915/pmu: Report frequency as zero while GPU is sleeping URL : https://patchwork.freedesktop.org/series/70168/ State : success == Summary == CI Bug Log - changes from CI_DRM_7438 -> Patchwork_15494 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/index.html Known issues ------------ Here are the changes found in Patchwork_15494 that come from known issues: ### IGT changes ### #### Possible fixes #### * igt@gem_ctx_create@basic-files: - {fi-tgl-u}: [INCOMPLETE][1] ([fdo#111735]) -> [PASS][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-tgl-u/igt@gem_ctx_create@basic-files.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-tgl-u/igt@gem_ctx_create@basic-files.html * igt@i915_pm_rpm@module-reload: - fi-skl-6770hq: [FAIL][3] ([fdo#108511]) -> [PASS][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html - fi-skl-lmem: [DMESG-WARN][5] ([fdo#112261]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html #### Warnings #### * igt@kms_busy@basic-flip-pipe-b: - fi-kbl-x1275: [DMESG-WARN][7] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][8] ([fdo#103558] / [fdo#105602]) +3 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy: - fi-kbl-x1275: [DMESG-WARN][9] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][10] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +6 similar issues [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html * igt@kms_flip@basic-flip-vs-dpms: - fi-icl-dsi: [INCOMPLETE][11] ([fdo#107713]) -> [DMESG-WARN][12] ([fdo#107724]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-icl-dsi/igt@kms_flip@basic-flip-vs-dpms.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-icl-dsi/igt@kms_flip@basic-flip-vs-dpms.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558 [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602 [fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511 [fdo#109964]: https://bugs.freedesktop.org/show_bug.cgi?id=109964 [fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735 [fdo#112260]: https://bugs.freedesktop.org/show_bug.cgi?id=112260 [fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261 [fdo#112298]: https://bugs.freedesktop.org/show_bug.cgi?id=112298 Participating hosts (51 -> 45) ------------------------------ Additional (1): fi-tgl-y Missing (7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7438 -> Patchwork_15494 CI-20190529: 20190529 CI_DRM_7438: 8a2661592e79e48bcba9c24565b2b16edafbcbaa @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5313: 92caadb4e551ba05aa6e6e567ef69da96ca7e328 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_15494: 2c5080a659dfb55e88db4fe01a6738dda0735610 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 2c5080a659df drm/i915/pmu: Report frequency as zero while GPU is sleeping == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pmu: Report frequency as zero while GPU is sleeping @ 2019-11-28 19:26 ` Patchwork 0 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2019-11-28 19:26 UTC (permalink / raw) To: Tvrtko Ursulin; +Cc: intel-gfx == Series Details == Series: drm/i915/pmu: Report frequency as zero while GPU is sleeping URL : https://patchwork.freedesktop.org/series/70168/ State : success == Summary == CI Bug Log - changes from CI_DRM_7438 -> Patchwork_15494 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/index.html Known issues ------------ Here are the changes found in Patchwork_15494 that come from known issues: ### IGT changes ### #### Possible fixes #### * igt@gem_ctx_create@basic-files: - {fi-tgl-u}: [INCOMPLETE][1] ([fdo#111735]) -> [PASS][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-tgl-u/igt@gem_ctx_create@basic-files.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-tgl-u/igt@gem_ctx_create@basic-files.html * igt@i915_pm_rpm@module-reload: - fi-skl-6770hq: [FAIL][3] ([fdo#108511]) -> [PASS][4] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html - fi-skl-lmem: [DMESG-WARN][5] ([fdo#112261]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-skl-lmem/igt@i915_pm_rpm@module-reload.html #### Warnings #### * igt@kms_busy@basic-flip-pipe-b: - fi-kbl-x1275: [DMESG-WARN][7] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][8] ([fdo#103558] / [fdo#105602]) +3 similar issues [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html * igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy: - fi-kbl-x1275: [DMESG-WARN][9] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][10] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +6 similar issues [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-kbl-x1275/igt@kms_cursor_legacy@basic-busy-flip-before-cursor-legacy.html * igt@kms_flip@basic-flip-vs-dpms: - fi-icl-dsi: [INCOMPLETE][11] ([fdo#107713]) -> [DMESG-WARN][12] ([fdo#107724]) [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7438/fi-icl-dsi/igt@kms_flip@basic-flip-vs-dpms.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/fi-icl-dsi/igt@kms_flip@basic-flip-vs-dpms.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558 [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602 [fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724 [fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511 [fdo#109964]: https://bugs.freedesktop.org/show_bug.cgi?id=109964 [fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735 [fdo#112260]: https://bugs.freedesktop.org/show_bug.cgi?id=112260 [fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261 [fdo#112298]: https://bugs.freedesktop.org/show_bug.cgi?id=112298 Participating hosts (51 -> 45) ------------------------------ Additional (1): fi-tgl-y Missing (7): fi-kbl-soraka fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7438 -> Patchwork_15494 CI-20190529: 20190529 CI_DRM_7438: 8a2661592e79e48bcba9c24565b2b16edafbcbaa @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5313: 92caadb4e551ba05aa6e6e567ef69da96ca7e328 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_15494: 2c5080a659dfb55e88db4fe01a6738dda0735610 @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 2c5080a659df drm/i915/pmu: Report frequency as zero while GPU is sleeping == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15494/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* ✓ Fi.CI.BAT: success for drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) @ 2019-11-29 18:38 ` Patchwork 0 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2019-11-29 18:38 UTC (permalink / raw) To: Tvrtko Ursulin; +Cc: intel-gfx == Series Details == Series: drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) URL : https://patchwork.freedesktop.org/series/70168/ State : success == Summary == CI Bug Log - changes from CI_DRM_7444 -> Patchwork_15509 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/index.html Known issues ------------ Here are the changes found in Patchwork_15509 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@i915_selftest@live_blt: - fi-hsw-peppy: [PASS][1] -> [DMESG-FAIL][2] ([fdo#112147]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-hsw-peppy/igt@i915_selftest@live_blt.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-hsw-peppy/igt@i915_selftest@live_blt.html * igt@kms_chamelium@hdmi-edid-read: - fi-kbl-7500u: [PASS][3] -> [FAIL][4] ([fdo#109483]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-kbl-7500u/igt@kms_chamelium@hdmi-edid-read.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-kbl-7500u/igt@kms_chamelium@hdmi-edid-read.html #### Possible fixes #### * igt@i915_module_load@reload-no-display: - fi-skl-lmem: [DMESG-WARN][5] ([fdo#112261]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-skl-lmem/igt@i915_module_load@reload-no-display.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-skl-lmem/igt@i915_module_load@reload-no-display.html * igt@i915_module_load@reload-with-fault-injection: - fi-icl-y: [INCOMPLETE][7] ([fdo#107713]) -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-y/igt@i915_module_load@reload-with-fault-injection.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-y/igt@i915_module_load@reload-with-fault-injection.html - fi-icl-u3: [INCOMPLETE][9] ([fdo#107713]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-u3/igt@i915_module_load@reload-with-fault-injection.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-u3/igt@i915_module_load@reload-with-fault-injection.html * igt@i915_pm_rpm@module-reload: - fi-skl-6770hq: [FAIL][11] ([fdo#108511]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html * igt@i915_selftest@live_hangcheck: - fi-icl-dsi: [INCOMPLETE][13] ([fdo#107713] / [fdo#108569]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html * igt@kms_frontbuffer_tracking@basic: - fi-icl-u2: [FAIL][15] ([fdo#103167]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html - fi-tgl-y: [FAIL][17] ([fdo#103167] / [fdo#112163]) -> [PASS][18] [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-tgl-y/igt@kms_frontbuffer_tracking@basic.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-tgl-y/igt@kms_frontbuffer_tracking@basic.html #### Warnings #### * igt@gem_exec_suspend@basic-s0: - fi-kbl-x1275: [DMESG-WARN][19] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][20] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +3 similar issues [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html * igt@kms_busy@basic-flip-pipe-b: - fi-kbl-x1275: [DMESG-WARN][21] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][22] ([fdo#103558] / [fdo#105602]) +2 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558 [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602 [fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511 [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569 [fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483 [fdo#112147]: https://bugs.freedesktop.org/show_bug.cgi?id=112147 [fdo#112163]: https://bugs.freedesktop.org/show_bug.cgi?id=112163 [fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261 Participating hosts (52 -> 46) ------------------------------ Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7444 -> Patchwork_15509 CI-20190529: 20190529 CI_DRM_7444: b51db4a957209a27e9c5d0bbd3ce2408ccee6c2c @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5318: 26ae6584ac03ad862d82f986302275a68bcccb29 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_15509: 349100ddf38210abd5bc55edd6feed5b6996131f @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 349100ddf382 drm/i915/pmu: Report frequency as zero while GPU is sleeping == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) @ 2019-11-29 18:38 ` Patchwork 0 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2019-11-29 18:38 UTC (permalink / raw) To: Tvrtko Ursulin; +Cc: intel-gfx == Series Details == Series: drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) URL : https://patchwork.freedesktop.org/series/70168/ State : success == Summary == CI Bug Log - changes from CI_DRM_7444 -> Patchwork_15509 ==================================================== Summary ------- **SUCCESS** No regressions found. External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/index.html Known issues ------------ Here are the changes found in Patchwork_15509 that come from known issues: ### IGT changes ### #### Issues hit #### * igt@i915_selftest@live_blt: - fi-hsw-peppy: [PASS][1] -> [DMESG-FAIL][2] ([fdo#112147]) [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-hsw-peppy/igt@i915_selftest@live_blt.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-hsw-peppy/igt@i915_selftest@live_blt.html * igt@kms_chamelium@hdmi-edid-read: - fi-kbl-7500u: [PASS][3] -> [FAIL][4] ([fdo#109483]) [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-kbl-7500u/igt@kms_chamelium@hdmi-edid-read.html [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-kbl-7500u/igt@kms_chamelium@hdmi-edid-read.html #### Possible fixes #### * igt@i915_module_load@reload-no-display: - fi-skl-lmem: [DMESG-WARN][5] ([fdo#112261]) -> [PASS][6] [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-skl-lmem/igt@i915_module_load@reload-no-display.html [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-skl-lmem/igt@i915_module_load@reload-no-display.html * igt@i915_module_load@reload-with-fault-injection: - fi-icl-y: [INCOMPLETE][7] ([fdo#107713]) -> [PASS][8] [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-y/igt@i915_module_load@reload-with-fault-injection.html [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-y/igt@i915_module_load@reload-with-fault-injection.html - fi-icl-u3: [INCOMPLETE][9] ([fdo#107713]) -> [PASS][10] [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-u3/igt@i915_module_load@reload-with-fault-injection.html [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-u3/igt@i915_module_load@reload-with-fault-injection.html * igt@i915_pm_rpm@module-reload: - fi-skl-6770hq: [FAIL][11] ([fdo#108511]) -> [PASS][12] [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-skl-6770hq/igt@i915_pm_rpm@module-reload.html * igt@i915_selftest@live_hangcheck: - fi-icl-dsi: [INCOMPLETE][13] ([fdo#107713] / [fdo#108569]) -> [PASS][14] [13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html [14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-dsi/igt@i915_selftest@live_hangcheck.html * igt@kms_frontbuffer_tracking@basic: - fi-icl-u2: [FAIL][15] ([fdo#103167]) -> [PASS][16] [15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html [16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-icl-u2/igt@kms_frontbuffer_tracking@basic.html - fi-tgl-y: [FAIL][17] ([fdo#103167] / [fdo#112163]) -> [PASS][18] [17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-tgl-y/igt@kms_frontbuffer_tracking@basic.html [18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-tgl-y/igt@kms_frontbuffer_tracking@basic.html #### Warnings #### * igt@gem_exec_suspend@basic-s0: - fi-kbl-x1275: [DMESG-WARN][19] ([fdo#103558] / [fdo#105602]) -> [DMESG-WARN][20] ([fdo#103558] / [fdo#105602] / [fdo#105763]) +3 similar issues [19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html [20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-kbl-x1275/igt@gem_exec_suspend@basic-s0.html * igt@kms_busy@basic-flip-pipe-b: - fi-kbl-x1275: [DMESG-WARN][21] ([fdo#103558] / [fdo#105602] / [fdo#105763]) -> [DMESG-WARN][22] ([fdo#103558] / [fdo#105602]) +2 similar issues [21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html [22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/fi-kbl-x1275/igt@kms_busy@basic-flip-pipe-b.html [fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167 [fdo#103558]: https://bugs.freedesktop.org/show_bug.cgi?id=103558 [fdo#105602]: https://bugs.freedesktop.org/show_bug.cgi?id=105602 [fdo#105763]: https://bugs.freedesktop.org/show_bug.cgi?id=105763 [fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713 [fdo#108511]: https://bugs.freedesktop.org/show_bug.cgi?id=108511 [fdo#108569]: https://bugs.freedesktop.org/show_bug.cgi?id=108569 [fdo#109483]: https://bugs.freedesktop.org/show_bug.cgi?id=109483 [fdo#112147]: https://bugs.freedesktop.org/show_bug.cgi?id=112147 [fdo#112163]: https://bugs.freedesktop.org/show_bug.cgi?id=112163 [fdo#112261]: https://bugs.freedesktop.org/show_bug.cgi?id=112261 Participating hosts (52 -> 46) ------------------------------ Missing (6): fi-ilk-m540 fi-hsw-4200u fi-bsw-cyan fi-ctg-p8600 fi-byt-clapper fi-bdw-samus Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7444 -> Patchwork_15509 CI-20190529: 20190529 CI_DRM_7444: b51db4a957209a27e9c5d0bbd3ce2408ccee6c2c @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5318: 26ae6584ac03ad862d82f986302275a68bcccb29 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_15509: 349100ddf38210abd5bc55edd6feed5b6996131f @ git://anongit.freedesktop.org/gfx-ci/linux == Linux commits == 349100ddf382 drm/i915/pmu: Report frequency as zero while GPU is sleeping == Logs == For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* ✗ Fi.CI.IGT: failure for drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) @ 2019-11-30 17:52 ` Patchwork 0 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2019-11-30 17:52 UTC (permalink / raw) To: Tvrtko Ursulin; +Cc: intel-gfx == Series Details == Series: drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) URL : https://patchwork.freedesktop.org/series/70168/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7444_full -> Patchwork_15509_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_15509_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_15509_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_15509_full: ### IGT changes ### #### Possible regressions #### * igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled: - shard-skl: [PASS][1] -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl8/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl8/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * {igt@gem_exec_schedule@pi-shared-iova-bsd}: - shard-iclb: NOTRUN -> [SKIP][3] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_exec_schedule@pi-shared-iova-bsd.html Known issues ------------ Here are the changes found in Patchwork_15509_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_busy@busy-vcs1: - shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#112080]) +4 similar issues [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb1/igt@gem_busy@busy-vcs1.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb3/igt@gem_busy@busy-vcs1.html * igt@gem_ctx_isolation@bcs0-s3: - shard-tglb: [PASS][6] -> [INCOMPLETE][7] ([i915#456]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb4/igt@gem_ctx_isolation@bcs0-s3.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb8/igt@gem_ctx_isolation@bcs0-s3.html * igt@gem_ctx_persistence@vcs1-cleanup: - shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#109276] / [fdo#112080]) +1 similar issue [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb1/igt@gem_ctx_persistence@vcs1-cleanup.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb3/igt@gem_ctx_persistence@vcs1-cleanup.html * igt@gem_eio@in-flight-suspend: - shard-skl: [PASS][10] -> [INCOMPLETE][11] ([i915#69]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl1/igt@gem_eio@in-flight-suspend.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl6/igt@gem_eio@in-flight-suspend.html * igt@gem_exec_schedule@preempt-queue-bsd1: - shard-iclb: [PASS][12] -> [SKIP][13] ([fdo#109276]) +3 similar issues [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb1/igt@gem_exec_schedule@preempt-queue-bsd1.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb3/igt@gem_exec_schedule@preempt-queue-bsd1.html * igt@gem_exec_schedule@preempt-queue-bsd2: - shard-tglb: [PASS][14] -> [INCOMPLETE][15] ([fdo#111606] / [fdo#111677]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb4/igt@gem_exec_schedule@preempt-queue-bsd2.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb6/igt@gem_exec_schedule@preempt-queue-bsd2.html * igt@gem_exec_schedule@preempt-queue-chain-vebox: - shard-glk: [PASS][16] -> [INCOMPLETE][17] ([i915#58] / [k.org#198133]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-glk4/igt@gem_exec_schedule@preempt-queue-chain-vebox.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-glk5/igt@gem_exec_schedule@preempt-queue-chain-vebox.html * igt@gem_exec_schedule@wide-bsd: - shard-iclb: [PASS][18] -> [SKIP][19] ([fdo#112146]) +2 similar issues [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@gem_exec_schedule@wide-bsd.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_exec_schedule@wide-bsd.html * igt@gem_exec_suspend@basic-s3: - shard-kbl: [PASS][20] -> [DMESG-WARN][21] ([i915#180]) +1 similar issue [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl3/igt@gem_exec_suspend@basic-s3.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl6/igt@gem_exec_suspend@basic-s3.html * igt@gem_ppgtt@flink-and-close-vma-leak: - shard-kbl: [PASS][22] -> [FAIL][23] ([i915#644]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl6/igt@gem_ppgtt@flink-and-close-vma-leak.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl1/igt@gem_ppgtt@flink-and-close-vma-leak.html * igt@gem_userptr_blits@sync-unmap-after-close: - shard-hsw: [PASS][24] -> [DMESG-WARN][25] ([fdo#111870]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw8/igt@gem_userptr_blits@sync-unmap-after-close.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw8/igt@gem_userptr_blits@sync-unmap-after-close.html * igt@i915_pm_rpm@modeset-stress-extra-wait: - shard-glk: [PASS][26] -> [DMESG-WARN][27] ([i915#118] / [i915#95]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-glk5/igt@i915_pm_rpm@modeset-stress-extra-wait.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-glk8/igt@i915_pm_rpm@modeset-stress-extra-wait.html * igt@kms_color@pipe-a-ctm-0-75: - shard-skl: [PASS][28] -> [DMESG-WARN][29] ([i915#109]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl10/igt@kms_color@pipe-a-ctm-0-75.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl10/igt@kms_color@pipe-a-ctm-0-75.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff: - shard-tglb: [PASS][30] -> [INCOMPLETE][31] ([i915#435] / [i915#474]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html - shard-iclb: [PASS][32] -> [INCOMPLETE][33] ([i915#140]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html * igt@kms_frontbuffer_tracking@fbc-suspend: - shard-apl: [PASS][34] -> [DMESG-WARN][35] ([i915#180]) +2 similar issues [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl1/igt@kms_frontbuffer_tracking@fbc-suspend.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl1/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite: - shard-iclb: [PASS][36] -> [FAIL][37] ([i915#49]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite.html * igt@kms_plane@pixel-format-pipe-b-planes-source-clamping: - shard-kbl: [PASS][38] -> [INCOMPLETE][39] ([fdo#103665] / [i915#435]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl6/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl1/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [PASS][40] -> [FAIL][41] ([fdo#108145] / [i915#265]) [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl8/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_vblank@pipe-d-ts-continuation-suspend: - shard-tglb: [PASS][42] -> [INCOMPLETE][43] ([i915#460]) [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb6/igt@kms_vblank@pipe-d-ts-continuation-suspend.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb7/igt@kms_vblank@pipe-d-ts-continuation-suspend.html #### Possible fixes #### * igt@gem_busy@extended-parallel-vcs1: - shard-iclb: [SKIP][44] ([fdo#112080]) -> [PASS][45] +5 similar issues [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@gem_busy@extended-parallel-vcs1.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_busy@extended-parallel-vcs1.html * igt@gem_ctx_isolation@vcs1-none: - shard-iclb: [SKIP][46] ([fdo#109276] / [fdo#112080]) -> [PASS][47] +1 similar issue [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb5/igt@gem_ctx_isolation@vcs1-none.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_ctx_isolation@vcs1-none.html * igt@gem_exec_balancer@indices: - shard-skl: [INCOMPLETE][48] -> [PASS][49] [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl8/igt@gem_exec_balancer@indices.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl2/igt@gem_exec_balancer@indices.html * igt@gem_exec_reloc@basic-wc-cpu-active: - shard-skl: [DMESG-WARN][50] ([i915#109]) -> [PASS][51] [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl6/igt@gem_exec_reloc@basic-wc-cpu-active.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl3/igt@gem_exec_reloc@basic-wc-cpu-active.html * igt@gem_exec_schedule@preempt-contexts-bsd2: - shard-iclb: [SKIP][52] ([fdo#109276]) -> [PASS][53] +8 similar issues [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb3/igt@gem_exec_schedule@preempt-contexts-bsd2.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb1/igt@gem_exec_schedule@preempt-contexts-bsd2.html * igt@gem_exec_schedule@preempt-other-chain-bsd: - shard-iclb: [SKIP][54] ([fdo#112146]) -> [PASS][55] [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb2/igt@gem_exec_schedule@preempt-other-chain-bsd.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb8/igt@gem_exec_schedule@preempt-other-chain-bsd.html * igt@gem_exec_schedule@preempt-queue-chain-bsd2: - shard-tglb: [INCOMPLETE][56] ([fdo#111677]) -> [PASS][57] [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb6/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb4/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html * igt@gem_persistent_relocs@forked-thrashing: - shard-snb: [FAIL][58] ([i915#520]) -> [PASS][59] [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-snb5/igt@gem_persistent_relocs@forked-thrashing.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-snb6/igt@gem_persistent_relocs@forked-thrashing.html * igt@gem_softpin@noreloc-s3: - shard-apl: [DMESG-WARN][60] ([i915#180]) -> [PASS][61] [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl6/igt@gem_softpin@noreloc-s3.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl8/igt@gem_softpin@noreloc-s3.html * igt@gem_userptr_blits@map-fixed-invalidate-busy: - shard-snb: [DMESG-WARN][62] ([fdo#111870]) -> [PASS][63] [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html - shard-hsw: [DMESG-WARN][64] ([fdo#111870]) -> [PASS][65] +1 similar issue [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html * igt@gem_workarounds@suspend-resume-fd: - shard-kbl: [DMESG-WARN][66] ([i915#180]) -> [PASS][67] +9 similar issues [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl7/igt@gem_workarounds@suspend-resume-fd.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl6/igt@gem_workarounds@suspend-resume-fd.html - shard-tglb: [INCOMPLETE][68] ([i915#456] / [i915#460]) -> [PASS][69] +2 similar issues [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb4/igt@gem_workarounds@suspend-resume-fd.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb7/igt@gem_workarounds@suspend-resume-fd.html * igt@kms_flip@flip-vs-suspend: - shard-hsw: [INCOMPLETE][70] ([i915#61]) -> [PASS][71] [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw4/igt@kms_flip@flip-vs-suspend.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw8/igt@kms_flip@flip-vs-suspend.html * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render: - shard-iclb: [FAIL][72] ([i915#49]) -> [PASS][73] +2 similar issues [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move: - shard-tglb: [INCOMPLETE][74] ([i915#474]) -> [PASS][75] +1 similar issue [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html * igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary: - shard-kbl: [INCOMPLETE][76] ([fdo#103665] / [i915#634]) -> [PASS][77] [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite: - shard-iclb: [INCOMPLETE][78] ([i915#123] / [i915#140]) -> [PASS][79] +2 similar issues [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt: - shard-skl: [INCOMPLETE][80] ([i915#123]) -> [PASS][81] [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [FAIL][82] ([fdo#108145] / [i915#265]) -> [PASS][83] [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl6/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl3/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_setmode@basic: - shard-apl: [FAIL][84] ([i915#31]) -> [PASS][85] [84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl6/igt@kms_setmode@basic.html [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl6/igt@kms_setmode@basic.html * {igt@perf_pmu@frequency-idle}: - shard-apl: [FAIL][86] -> [PASS][87] [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl7/igt@perf_pmu@frequency-idle.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl2/igt@perf_pmu@frequency-idle.html - shard-glk: [FAIL][88] -> [PASS][89] [88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-glk9/igt@perf_pmu@frequency-idle.html [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-glk9/igt@perf_pmu@frequency-idle.html - shard-snb: [FAIL][90] -> [PASS][91] [90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-snb6/igt@perf_pmu@frequency-idle.html [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-snb5/igt@perf_pmu@frequency-idle.html - shard-skl: [FAIL][92] -> [PASS][93] [92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl7/igt@perf_pmu@frequency-idle.html [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl6/igt@perf_pmu@frequency-idle.html - shard-hsw: [FAIL][94] -> [PASS][95] [94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw8/igt@perf_pmu@frequency-idle.html [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw8/igt@perf_pmu@frequency-idle.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665 [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 [fdo#111606]: https://bugs.freedesktop.org/show_bug.cgi?id=111606 [fdo#111677]: https://bugs.freedesktop.org/show_bug.cgi?id=111677 [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870 [fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080 [fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146 [i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109 [i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118 [i915#123]: https://gitlab.freedesktop.org/drm/intel/issues/123 [i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 [i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31 [i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435 [i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456 [i915#460]: https://gitlab.freedesktop.org/drm/intel/issues/460 [i915#474]: https://gitlab.freedesktop.org/drm/intel/issues/474 [i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49 [i915#520]: https://gitlab.freedesktop.org/drm/intel/issues/520 [i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58 [i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61 [i915#634]: https://gitlab.freedesktop.org/drm/intel/issues/634 [i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644 [i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69 [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95 [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133 Participating hosts (11 -> 11) ------------------------------ No changes in participating hosts Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7444 -> Patchwork_15509 CI-20190529: 20190529 CI_DRM_7444: b51db4a957209a27e9c5d0bbd3ce2408ccee6c2c @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5318: 26ae6584ac03ad862d82f986302275a68bcccb29 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_15509: 349100ddf38210abd5bc55edd6feed5b6996131f @ 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_15509/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) @ 2019-11-30 17:52 ` Patchwork 0 siblings, 0 replies; 19+ messages in thread From: Patchwork @ 2019-11-30 17:52 UTC (permalink / raw) To: Tvrtko Ursulin; +Cc: intel-gfx == Series Details == Series: drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) URL : https://patchwork.freedesktop.org/series/70168/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7444_full -> Patchwork_15509_full ==================================================== Summary ------- **FAILURE** Serious unknown changes coming with Patchwork_15509_full absolutely need to be verified manually. If you think the reported changes have nothing to do with the changes introduced in Patchwork_15509_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_15509_full: ### IGT changes ### #### Possible regressions #### * igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled: - shard-skl: [PASS][1] -> [INCOMPLETE][2] [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl8/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl8/igt@kms_draw_crc@draw-method-xrgb2101010-render-ytiled.html #### Suppressed #### The following results come from untrusted machines, tests, or statuses. They do not affect the overall result. * {igt@gem_exec_schedule@pi-shared-iova-bsd}: - shard-iclb: NOTRUN -> [SKIP][3] [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_exec_schedule@pi-shared-iova-bsd.html Known issues ------------ Here are the changes found in Patchwork_15509_full that come from known issues: ### IGT changes ### #### Issues hit #### * igt@gem_busy@busy-vcs1: - shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#112080]) +4 similar issues [4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb1/igt@gem_busy@busy-vcs1.html [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb3/igt@gem_busy@busy-vcs1.html * igt@gem_ctx_isolation@bcs0-s3: - shard-tglb: [PASS][6] -> [INCOMPLETE][7] ([i915#456]) [6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb4/igt@gem_ctx_isolation@bcs0-s3.html [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb8/igt@gem_ctx_isolation@bcs0-s3.html * igt@gem_ctx_persistence@vcs1-cleanup: - shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#109276] / [fdo#112080]) +1 similar issue [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb1/igt@gem_ctx_persistence@vcs1-cleanup.html [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb3/igt@gem_ctx_persistence@vcs1-cleanup.html * igt@gem_eio@in-flight-suspend: - shard-skl: [PASS][10] -> [INCOMPLETE][11] ([i915#69]) [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl1/igt@gem_eio@in-flight-suspend.html [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl6/igt@gem_eio@in-flight-suspend.html * igt@gem_exec_schedule@preempt-queue-bsd1: - shard-iclb: [PASS][12] -> [SKIP][13] ([fdo#109276]) +3 similar issues [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb1/igt@gem_exec_schedule@preempt-queue-bsd1.html [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb3/igt@gem_exec_schedule@preempt-queue-bsd1.html * igt@gem_exec_schedule@preempt-queue-bsd2: - shard-tglb: [PASS][14] -> [INCOMPLETE][15] ([fdo#111606] / [fdo#111677]) [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb4/igt@gem_exec_schedule@preempt-queue-bsd2.html [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb6/igt@gem_exec_schedule@preempt-queue-bsd2.html * igt@gem_exec_schedule@preempt-queue-chain-vebox: - shard-glk: [PASS][16] -> [INCOMPLETE][17] ([i915#58] / [k.org#198133]) [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-glk4/igt@gem_exec_schedule@preempt-queue-chain-vebox.html [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-glk5/igt@gem_exec_schedule@preempt-queue-chain-vebox.html * igt@gem_exec_schedule@wide-bsd: - shard-iclb: [PASS][18] -> [SKIP][19] ([fdo#112146]) +2 similar issues [18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@gem_exec_schedule@wide-bsd.html [19]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_exec_schedule@wide-bsd.html * igt@gem_exec_suspend@basic-s3: - shard-kbl: [PASS][20] -> [DMESG-WARN][21] ([i915#180]) +1 similar issue [20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl3/igt@gem_exec_suspend@basic-s3.html [21]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl6/igt@gem_exec_suspend@basic-s3.html * igt@gem_ppgtt@flink-and-close-vma-leak: - shard-kbl: [PASS][22] -> [FAIL][23] ([i915#644]) [22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl6/igt@gem_ppgtt@flink-and-close-vma-leak.html [23]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl1/igt@gem_ppgtt@flink-and-close-vma-leak.html * igt@gem_userptr_blits@sync-unmap-after-close: - shard-hsw: [PASS][24] -> [DMESG-WARN][25] ([fdo#111870]) [24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw8/igt@gem_userptr_blits@sync-unmap-after-close.html [25]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw8/igt@gem_userptr_blits@sync-unmap-after-close.html * igt@i915_pm_rpm@modeset-stress-extra-wait: - shard-glk: [PASS][26] -> [DMESG-WARN][27] ([i915#118] / [i915#95]) [26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-glk5/igt@i915_pm_rpm@modeset-stress-extra-wait.html [27]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-glk8/igt@i915_pm_rpm@modeset-stress-extra-wait.html * igt@kms_color@pipe-a-ctm-0-75: - shard-skl: [PASS][28] -> [DMESG-WARN][29] ([i915#109]) [28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl10/igt@kms_color@pipe-a-ctm-0-75.html [29]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl10/igt@kms_color@pipe-a-ctm-0-75.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff: - shard-tglb: [PASS][30] -> [INCOMPLETE][31] ([i915#435] / [i915#474]) [30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html [31]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html - shard-iclb: [PASS][32] -> [INCOMPLETE][33] ([i915#140]) [32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html [33]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-onoff.html * igt@kms_frontbuffer_tracking@fbc-suspend: - shard-apl: [PASS][34] -> [DMESG-WARN][35] ([i915#180]) +2 similar issues [34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl1/igt@kms_frontbuffer_tracking@fbc-suspend.html [35]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl1/igt@kms_frontbuffer_tracking@fbc-suspend.html * igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite: - shard-iclb: [PASS][36] -> [FAIL][37] ([i915#49]) [36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite.html [37]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-pri-indfb-draw-pwrite.html * igt@kms_plane@pixel-format-pipe-b-planes-source-clamping: - shard-kbl: [PASS][38] -> [INCOMPLETE][39] ([fdo#103665] / [i915#435]) [38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl6/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html [39]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl1/igt@kms_plane@pixel-format-pipe-b-planes-source-clamping.html * igt@kms_plane_alpha_blend@pipe-b-coverage-7efc: - shard-skl: [PASS][40] -> [FAIL][41] ([fdo#108145] / [i915#265]) [40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl8/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html [41]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl5/igt@kms_plane_alpha_blend@pipe-b-coverage-7efc.html * igt@kms_vblank@pipe-d-ts-continuation-suspend: - shard-tglb: [PASS][42] -> [INCOMPLETE][43] ([i915#460]) [42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb6/igt@kms_vblank@pipe-d-ts-continuation-suspend.html [43]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb7/igt@kms_vblank@pipe-d-ts-continuation-suspend.html #### Possible fixes #### * igt@gem_busy@extended-parallel-vcs1: - shard-iclb: [SKIP][44] ([fdo#112080]) -> [PASS][45] +5 similar issues [44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@gem_busy@extended-parallel-vcs1.html [45]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_busy@extended-parallel-vcs1.html * igt@gem_ctx_isolation@vcs1-none: - shard-iclb: [SKIP][46] ([fdo#109276] / [fdo#112080]) -> [PASS][47] +1 similar issue [46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb5/igt@gem_ctx_isolation@vcs1-none.html [47]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@gem_ctx_isolation@vcs1-none.html * igt@gem_exec_balancer@indices: - shard-skl: [INCOMPLETE][48] -> [PASS][49] [48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl8/igt@gem_exec_balancer@indices.html [49]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl2/igt@gem_exec_balancer@indices.html * igt@gem_exec_reloc@basic-wc-cpu-active: - shard-skl: [DMESG-WARN][50] ([i915#109]) -> [PASS][51] [50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl6/igt@gem_exec_reloc@basic-wc-cpu-active.html [51]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl3/igt@gem_exec_reloc@basic-wc-cpu-active.html * igt@gem_exec_schedule@preempt-contexts-bsd2: - shard-iclb: [SKIP][52] ([fdo#109276]) -> [PASS][53] +8 similar issues [52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb3/igt@gem_exec_schedule@preempt-contexts-bsd2.html [53]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb1/igt@gem_exec_schedule@preempt-contexts-bsd2.html * igt@gem_exec_schedule@preempt-other-chain-bsd: - shard-iclb: [SKIP][54] ([fdo#112146]) -> [PASS][55] [54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb2/igt@gem_exec_schedule@preempt-other-chain-bsd.html [55]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb8/igt@gem_exec_schedule@preempt-other-chain-bsd.html * igt@gem_exec_schedule@preempt-queue-chain-bsd2: - shard-tglb: [INCOMPLETE][56] ([fdo#111677]) -> [PASS][57] [56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb6/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html [57]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb4/igt@gem_exec_schedule@preempt-queue-chain-bsd2.html * igt@gem_persistent_relocs@forked-thrashing: - shard-snb: [FAIL][58] ([i915#520]) -> [PASS][59] [58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-snb5/igt@gem_persistent_relocs@forked-thrashing.html [59]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-snb6/igt@gem_persistent_relocs@forked-thrashing.html * igt@gem_softpin@noreloc-s3: - shard-apl: [DMESG-WARN][60] ([i915#180]) -> [PASS][61] [60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl6/igt@gem_softpin@noreloc-s3.html [61]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl8/igt@gem_softpin@noreloc-s3.html * igt@gem_userptr_blits@map-fixed-invalidate-busy: - shard-snb: [DMESG-WARN][62] ([fdo#111870]) -> [PASS][63] [62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [63]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-snb5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html - shard-hsw: [DMESG-WARN][64] ([fdo#111870]) -> [PASS][65] +1 similar issue [64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw5/igt@gem_userptr_blits@map-fixed-invalidate-busy.html [65]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html * igt@gem_workarounds@suspend-resume-fd: - shard-kbl: [DMESG-WARN][66] ([i915#180]) -> [PASS][67] +9 similar issues [66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl7/igt@gem_workarounds@suspend-resume-fd.html [67]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl6/igt@gem_workarounds@suspend-resume-fd.html - shard-tglb: [INCOMPLETE][68] ([i915#456] / [i915#460]) -> [PASS][69] +2 similar issues [68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb4/igt@gem_workarounds@suspend-resume-fd.html [69]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb7/igt@gem_workarounds@suspend-resume-fd.html * igt@kms_flip@flip-vs-suspend: - shard-hsw: [INCOMPLETE][70] ([i915#61]) -> [PASS][71] [70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw4/igt@kms_flip@flip-vs-suspend.html [71]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw8/igt@kms_flip@flip-vs-suspend.html * igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render: - shard-iclb: [FAIL][72] ([i915#49]) -> [PASS][73] +2 similar issues [72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html [73]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-offscren-pri-indfb-draw-render.html * igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move: - shard-tglb: [INCOMPLETE][74] ([i915#474]) -> [PASS][75] +1 similar issue [74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-tglb8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html [75]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-tglb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-cur-indfb-move.html * igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary: - shard-kbl: [INCOMPLETE][76] ([fdo#103665] / [i915#634]) -> [PASS][77] [76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-kbl1/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html [77]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-kbl3/igt@kms_frontbuffer_tracking@fbc-indfb-scaledprimary.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite: - shard-iclb: [INCOMPLETE][78] ([i915#123] / [i915#140]) -> [PASS][79] +2 similar issues [78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-iclb3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html [79]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-iclb5/igt@kms_frontbuffer_tracking@psr-1p-primscrn-cur-indfb-draw-pwrite.html * igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt: - shard-skl: [INCOMPLETE][80] ([i915#123]) -> [PASS][81] [80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt.html [81]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-shrfb-pgflip-blt.html * igt@kms_plane_alpha_blend@pipe-c-coverage-7efc: - shard-skl: [FAIL][82] ([fdo#108145] / [i915#265]) -> [PASS][83] [82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl6/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html [83]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl3/igt@kms_plane_alpha_blend@pipe-c-coverage-7efc.html * igt@kms_setmode@basic: - shard-apl: [FAIL][84] ([i915#31]) -> [PASS][85] [84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl6/igt@kms_setmode@basic.html [85]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl6/igt@kms_setmode@basic.html * {igt@perf_pmu@frequency-idle}: - shard-apl: [FAIL][86] -> [PASS][87] [86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-apl7/igt@perf_pmu@frequency-idle.html [87]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-apl2/igt@perf_pmu@frequency-idle.html - shard-glk: [FAIL][88] -> [PASS][89] [88]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-glk9/igt@perf_pmu@frequency-idle.html [89]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-glk9/igt@perf_pmu@frequency-idle.html - shard-snb: [FAIL][90] -> [PASS][91] [90]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-snb6/igt@perf_pmu@frequency-idle.html [91]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-snb5/igt@perf_pmu@frequency-idle.html - shard-skl: [FAIL][92] -> [PASS][93] [92]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-skl7/igt@perf_pmu@frequency-idle.html [93]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-skl6/igt@perf_pmu@frequency-idle.html - shard-hsw: [FAIL][94] -> [PASS][95] [94]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7444/shard-hsw8/igt@perf_pmu@frequency-idle.html [95]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_15509/shard-hsw8/igt@perf_pmu@frequency-idle.html {name}: This element is suppressed. This means it is ignored when computing the status of the difference (SUCCESS, WARNING, or FAILURE). [fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665 [fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145 [fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276 [fdo#111606]: https://bugs.freedesktop.org/show_bug.cgi?id=111606 [fdo#111677]: https://bugs.freedesktop.org/show_bug.cgi?id=111677 [fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870 [fdo#112080]: https://bugs.freedesktop.org/show_bug.cgi?id=112080 [fdo#112146]: https://bugs.freedesktop.org/show_bug.cgi?id=112146 [i915#109]: https://gitlab.freedesktop.org/drm/intel/issues/109 [i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118 [i915#123]: https://gitlab.freedesktop.org/drm/intel/issues/123 [i915#140]: https://gitlab.freedesktop.org/drm/intel/issues/140 [i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180 [i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265 [i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31 [i915#435]: https://gitlab.freedesktop.org/drm/intel/issues/435 [i915#456]: https://gitlab.freedesktop.org/drm/intel/issues/456 [i915#460]: https://gitlab.freedesktop.org/drm/intel/issues/460 [i915#474]: https://gitlab.freedesktop.org/drm/intel/issues/474 [i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49 [i915#520]: https://gitlab.freedesktop.org/drm/intel/issues/520 [i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58 [i915#61]: https://gitlab.freedesktop.org/drm/intel/issues/61 [i915#634]: https://gitlab.freedesktop.org/drm/intel/issues/634 [i915#644]: https://gitlab.freedesktop.org/drm/intel/issues/644 [i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69 [i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95 [k.org#198133]: https://bugzilla.kernel.org/show_bug.cgi?id=198133 Participating hosts (11 -> 11) ------------------------------ No changes in participating hosts Build changes ------------- * CI: CI-20190529 -> None * Linux: CI_DRM_7444 -> Patchwork_15509 CI-20190529: 20190529 CI_DRM_7444: b51db4a957209a27e9c5d0bbd3ce2408ccee6c2c @ git://anongit.freedesktop.org/gfx-ci/linux IGT_5318: 26ae6584ac03ad862d82f986302275a68bcccb29 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools Patchwork_15509: 349100ddf38210abd5bc55edd6feed5b6996131f @ 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_15509/index.html _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx ^ permalink raw reply [flat|nested] 19+ messages in thread
end of thread, other threads:[~2019-12-06 13:04 UTC | newest] Thread overview: 19+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2019-11-28 16:10 [PATCH] drm/i915/pmu: Report frequency as zero while GPU is sleeping Tvrtko Ursulin 2019-11-28 16:10 ` [Intel-gfx] " Tvrtko Ursulin 2019-11-28 16:19 ` Chris Wilson 2019-11-28 16:19 ` [Intel-gfx] " Chris Wilson 2019-11-28 16:22 ` Chris Wilson 2019-11-28 16:22 ` [Intel-gfx] " Chris Wilson 2019-11-28 17:23 ` Tvrtko Ursulin 2019-11-28 17:23 ` [Intel-gfx] " Tvrtko Ursulin 2019-11-29 10:54 ` [PATCH v2] " Tvrtko Ursulin 2019-11-29 10:54 ` [Intel-gfx] " Tvrtko Ursulin 2019-12-06 12:32 ` Chris Wilson 2019-12-06 13:04 ` Tvrtko Ursulin 2019-12-06 12:33 ` Chris Wilson 2019-11-28 19:26 ` ✓ Fi.CI.BAT: success for " Patchwork 2019-11-28 19:26 ` [Intel-gfx] " Patchwork 2019-11-29 18:38 ` ✓ Fi.CI.BAT: success for drm/i915/pmu: Report frequency as zero while GPU is sleeping (rev2) Patchwork 2019-11-29 18:38 ` [Intel-gfx] " Patchwork 2019-11-30 17:52 ` ✗ Fi.CI.IGT: failure " Patchwork 2019-11-30 17:52 ` [Intel-gfx] " 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.