Consider DBuf bandwidth when calculating CDCLK
Subsystems (3)
v9 cover Consider DBuf bandwidth when calculating CDCLK
We need to calculate cdclk after watermarks/ddb has been calculated as with recent hw CDCLK needs to be adjusted accordingly to DBuf requirements, which is not possible with current code organization.
Setting CDCLK according to DBuf BW requirements and not just rejecting if it doesn't satisfy BW requirements, will allow us to save power when it is possible and gain additional bandwidth when it's needed - i.e boosting both our power management and perfomance capabilities.
This patch is preparation for that, first we now extract modeset calculation from modeset checks, in order to call it after wm/ddb has been calculated.
Stanislav Lisovskiy (7):
drm/i915: Decouple cdclk calculation from modeset checks drm/i915: Extract cdclk requirements checking to separate function drm/i915: Check plane configuration properly
drm/i915: Plane configuration affects CDCLK in Gen11+ drm/i915: Introduce for_each_dbuf_slice_in_mask macro drm/i915: Adjust CDCLK accordingly to our DBuf bw needs drm/i915: Remove unneeded hack now for CDCLK
drivers/gpu/drm/i915/display/intel_bw.c | 118 +++++++++++++++++- drivers/gpu/drm/i915/display/intel_bw.h | 10 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 40 +++--- drivers/gpu/drm/i915/display/intel_cdclk.h | 1 - drivers/gpu/drm/i915/display/intel_display.c | 89 ++++++++++--- drivers/gpu/drm/i915/display/intel_display.h | 7 ++ .../drm/i915/display/intel_display_power.h | 1 + drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 31 ++++- drivers/gpu/drm/i915/intel_pm.h | 3 + 10 files changed, 261 insertions(+), 40 deletions(-)
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 1/7 drm/i915: Decouple cdclk calculation from modeset checks
We need to calculate cdclk after watermarks/ddb has been calculated as with recent hw CDCLK needs to be adjusted accordingly to DBuf requirements, which is not possible with current code organization.
Setting CDCLK according to DBuf BW requirements and not just rejecting if it doesn't satisfy BW requirements, will allow us to save power when it is possible and gain additional bandwidth when it's needed - i.e boosting both our power management and perfomance capabilities.
This patch is preparation for that, first we now extract modeset calculation from modeset checks, in order to call it after wm/ddb has been calculated.
v2: - Extract only intel_modeset_calc_cdclk from intel_modeset_checks
(Ville Syrjälä)
v3: - Clear plls after intel_modeset_calc_cdclk
v4: - Added r-b from previous revision to commit message
--- drivers/gpu/drm/i915/display/intel_display.c | 22 +++++++++++--------- 1 file changed, 12 insertions(+), 10 deletions(-)
drivers/gpu/drm/i915/display/intel_display.c +12 -10
@@ -14493,12 +14493,6 @@ static int intel_modeset_checks(struct intel_atomic_state *state)return ret; } - ret =intel_modeset_calc_cdclk (state); -if (ret) -return ret; - -intel_modeset_clear_plls (state); -if (IS_HASWELL (dev_priv))return hsw_mode_set_planes_workaround (state);
@@ -14830,10 +14824,6 @@ static int intel_atomic_check(struct drm_device *dev, goto fail; } - ret =intel_atomic_check_crtcs (state); -if (ret) - goto fail; -intel_fbc_choose_crtc (dev_priv, state); ret =calc_watermark_data (state);if (ret)
@@ -14843,6 +14833,18 @@ static int intel_atomic_check(struct drm_device *dev,if (ret) goto fail; +if (any_ms) { + ret =intel_modeset_calc_cdclk (state); +if (ret) +return ret; + +intel_modeset_clear_plls (state); + } + + ret =intel_atomic_check_crtcs (state); +if (ret) + goto fail; +for_each_oldnew_intel_crtc_in_state (state, crtc, old_crtc_state, new_crtc_state, i) { if (!needs_modeset(new_crtc_state) &&
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 2/7 drm/i915: Extract cdclk requirements checking to separate function
In reply to Stanislav LisovskiyIn Gen11+ whenever we might exceed DBuf bandwidth we might need to recalculate CDCLK which DBuf bandwidth is scaled with. Total Dbuf bw used might change based on particular plane needs.
Thus to calculate if cdclk needs to be changed it is not enough anymore to check plane configuration and plane min cdclk, per DBuf bw can be calculated only after wm/ddb calculation is done and all required planes are added into the state. In order to keep all min_cdclk related checks in one place let's extract it into separate function, checking and modifying any_ms.
--- drivers/gpu/drm/i915/display/intel_display.c | 30 ++++++++++++++------ 1 file changed, 22 insertions(+), 8 deletions(-)
drivers/gpu/drm/i915/display/intel_display.c +22 -8
@@ -14572,8 +14572,7 @@ static bool active_planes_affects_min_cdclk(struct drm_i915_private *dev_priv)IS_IVYBRIDGE (dev_priv); } -static int intel_atomic_check_planes (struct intel_atomic_state *state, -bool *need_cdclk_calc) +static int intel_atomic_check_planes (struct intel_atomic_state *state) {struct drm_i915_private *dev_priv =to_i915 (state->base.dev);struct intel_crtc_state *old_crtc_state, *new_crtc_state;
@@ -14623,6 +14622,22 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state,return ret; } +return 0 ; +} + +static int intel_atomic_check_cdclk (struct intel_atomic_state *state, +bool *need_cdclk_calc) +{ +struct intel_cdclk_state *new_cdclk_state; +int i; +struct intel_plane_state *plane_state; +struct intel_plane *plane; +int ret; + + new_cdclk_state =intel_atomic_get_new_cdclk_state (state); +if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) + *need_cdclk_calc = true; +/* * active_planes bitmask has been updated, and potentially * affected planes are part of the state. We can now
@@ -14685,7 +14700,6 @@ static int intel_atomic_check(struct drm_device *dev,struct drm_i915_private *dev_priv =to_i915 (dev);struct intel_atomic_state *state =to_intel_atomic_state (_state);struct intel_crtc_state *old_crtc_state, *new_crtc_state; -struct intel_cdclk_state *new_cdclk_state;struct intel_crtc *crtc;int ret, i;bool any_ms = false;
@@ -14796,14 +14810,10 @@ static int intel_atomic_check(struct drm_device *dev,if (ret) goto fail; - ret =intel_atomic_check_planes (state, &any_ms); + ret =intel_atomic_check_planes (state);if (ret) goto fail; - new_cdclk_state =intel_atomic_get_new_cdclk_state (state); -if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) - any_ms = true; -/* * distrust_bios_wm will force a full dbuf recomputation * but the hardware state will only get updated accordingly
@@ -14833,6 +14843,10 @@ static int intel_atomic_check(struct drm_device *dev,if (ret) goto fail; + ret =intel_atomic_check_cdclk (state, &any_ms); +if (ret) + goto fail; +if (any_ms) { ret =intel_modeset_calc_cdclk (state);if (ret)
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 3/7 drm/i915: Check plane configuration properly
In reply to Stanislav LisovskiyFrom: Stanislav Lisovskiy <[email protected]>
Checking with hweight8 if plane configuration had changed seems to be wrong as different plane configs can result in a same hamming weight.
So lets check the bitmask itself.
--- drivers/gpu/drm/i915/display/intel_display.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display.c +7 -1
@@ -14614,7 +14614,13 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state) old_active_planes = old_crtc_state->active_planes & ~BIT (PLANE_CURSOR ); new_active_planes = new_crtc_state->active_planes & ~BIT (PLANE_CURSOR ); -if (hweight8 (old_active_planes) ==hweight8 (new_active_planes)) +/* +* Not only the number of planes, but if the plane configuration had +* changed might already mean we need to recompute min CDCLK, +* because different planes might consume different amount of Dbuf bandwidth +* according to formula: Bw per plane = Pixel rate * bpp * pipe/plane scale factor +*/ +if (old_active_planes == new_active_planes)continue ; ret =intel_crtc_add_planes_to_state (state, crtc, new_active_planes);
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 3/7 drm/i915: Check plane configuration properly
Checking with hweight8 if plane configuration had changed seems to be wrong as different plane configs can result in a same hamming weight.
So lets check the bitmask itself.
v2: Fixed "from" field which got corrupted for some weird reason
--- drivers/gpu/drm/i915/display/intel_display.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display.c +7 -1
@@ -14683,7 +14683,13 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state) old_active_planes = old_crtc_state->active_planes & ~BIT (PLANE_CURSOR ); new_active_planes = new_crtc_state->active_planes & ~BIT (PLANE_CURSOR ); -if (hweight8 (old_active_planes) ==hweight8 (new_active_planes)) +/* +* Not only the number of planes, but if the plane configuration had +* changed might already mean we need to recompute min CDCLK, +* because different planes might consume different amount of Dbuf bandwidth +* according to formula: Bw per plane = Pixel rate * bpp * pipe/plane scale factor +*/ +if (old_active_planes == new_active_planes)continue ; ret =intel_crtc_add_planes_to_state (state, crtc, new_active_planes);
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 4/7 drm/i915: Plane configuration affects CDCLK in Gen11+
In reply to Stanislav LisovskiyFrom: Stanislav Lisovskiy <[email protected]>
So lets support it.
--- drivers/gpu/drm/i915/display/intel_display.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display.c +1 -1
@@ -14569,7 +14569,7 @@ static bool active_planes_affects_min_cdclk(struct drm_i915_private *dev_priv)/* See {hsw,vlv,ivb}_plane_ratio() */ return IS_BROADWELL (dev_priv) ||IS_HASWELL (dev_priv) ||IS_CHERRYVIEW (dev_priv) ||IS_VALLEYVIEW (dev_priv) || -IS_IVYBRIDGE (dev_priv); +IS_IVYBRIDGE (dev_priv) || (INTEL_GEN (dev_priv) >=11 ); }static int intel_atomic_check_planes (struct intel_atomic_state *state)
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 4/7 drm/i915: Plane configuration affects CDCLK in Gen11+
So lets support it.
v2: - Fixed "from" field which got corrupted for some weird reason
--- drivers/gpu/drm/i915/display/intel_display.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/i915/display/intel_display.c +1 -1
@@ -14638,7 +14638,7 @@ static bool active_planes_affects_min_cdclk(struct drm_i915_private *dev_priv)/* See {hsw,vlv,ivb}_plane_ratio() */ return IS_BROADWELL (dev_priv) ||IS_HASWELL (dev_priv) ||IS_CHERRYVIEW (dev_priv) ||IS_VALLEYVIEW (dev_priv) || -IS_IVYBRIDGE (dev_priv); +IS_IVYBRIDGE (dev_priv) || (INTEL_GEN (dev_priv) >=11 ); }static int intel_atomic_check_planes (struct intel_atomic_state *state)
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 5/7 drm/i915: Introduce for_each_dbuf_slice_in_mask macro
In reply to Stanislav LisovskiyWe quite often need now to iterate only particular dbuf slices in mask, whether they are active or related to particular crtc.
v2: - Minor code refactoring
v3: - Use enum for max slices instead of macro
Let's make our life a bit easier and use a macro for that.
--- drivers/gpu/drm/i915/display/intel_display.h | 7 +++++++ drivers/gpu/drm/i915/display/intel_display_power.h | 1 + 2 files changed, 8 insertions(+)
drivers/gpu/drm/i915/display/intel_display.h +7 -0
@@ -187,6 +187,13 @@ enum plane_id {for ((__p) =PLANE_PRIMARY ; (__p) <I915_MAX_PLANES ; (__p)++) \ for_each_if((__crtc)->plane_ids_mask & BIT(__p)) +#define for_each_dbuf_slice_in_mask (__slice, __mask) \ + for ((__slice) = DBUF_S1; (__slice) < I915_MAX_DBUF_SLICES; (__slice)++) \ + for_each_if((BIT(__slice)) & (__mask)) + +#define for_each_dbuf_slice (__slice) \ + for_each_dbuf_slice_in_mask(__slice, BIT(I915_MAX_DBUF_SLICES) - 1) +enum port {PORT_NONE =-1 ,
drivers/gpu/drm/i915/display/intel_display_power.h +1 -0
@@ -314,6 +314,7 @@ intel_display_power_put_async(struct drm_i915_private *i915,enum dbuf_slice {DBUF_S1 ,DBUF_S2 , +I915_MAX_DBUF_SLICES };#define with_intel_display_power (i915, domain, wf) \
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 6/7 drm/i915: Adjust CDCLK accordingly to our DBuf bw needs
In reply to Stanislav LisovskiyAccording to BSpec max BW per slice is calculated using formula Max BW = CDCLK * 64. Currently when calculating min CDCLK we account only per plane requirements, however in order to avoid FIFO underruns we need to estimate accumulated BW consumed by all planes(ddb entries basically) residing on that particular DBuf slice. This will allow us to put CDCLK lower and save power when we don't need that much bandwidth or gain additional performance once plane consumption grows.
v2: - Fix long line warning
- Limited new DBuf bw checks to only gens >= 11
v3: - Lets track used Dbuf bw per slice and per crtc in bw state
(or may be in DBuf state in future), that way we don't need to have all crtcs in state and those only if we detect if are actually going to change cdclk, just same way as we do with other stuff, i.e intel_atomic_serialize_global_state and co. Just as per Ville's paradigm.
- Made dbuf bw calculation procedure look nicer by introducing for_each_dbuf_slice_in_mask - we often will now need to iterate slices using mask.
- According to experimental results CDCLK * 64 accounts for overall bandwidth across all dbufs, not per dbuf.
v4: - Fixed missing const(Ville)
- Removed spurious whitespaces(Ville)
- Fixed local variable init(reduced scope where not needed)
- Added some comments about data rate for planar formats
- Changed struct intel_crtc_bw to intel_dbuf_bw
- Moved dbuf bw calculation to intel_compute_min_cdclk(Ville)
v5: - Removed unneeded macro
v6: - Prevent too frequent CDCLK switching back and forth:
Always switch to higher CDCLK when needed to prevent bandwidth issues, however don't switch to lower CDCLK earlier than once in 30 minutes in order to prevent constant modeset blinking. We could of course not switch back at all, however this is bad from power consumption point of view.
v7: - Fixed to track cdclk using bw_state, modeset will be now
triggered only when CDCLK change is really needed.
v8: - Lock global state if bw_state->min_cdclk is changed.
- Try getting bw_state only if there are crtcs in the commit (need to have read-locked global state)
v9: - Do not do Dbuf bw check for gens < 9 - triggers WARN
as ddb_size is 0.
v10: - Lock global state for older gens as well.
v11: - Define new bw_calc_min_cdclk hook, instead of using
a condition(Manasi Navare)
--- drivers/gpu/drm/i915/display/intel_bw.c | 118 ++++++++++++++++++- drivers/gpu/drm/i915/display/intel_bw.h | 10 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 28 ++++- drivers/gpu/drm/i915/display/intel_cdclk.h | 1 - drivers/gpu/drm/i915/display/intel_display.c | 39 +++++- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 31 ++++- drivers/gpu/drm/i915/intel_pm.h | 3 + 8 files changed, 217 insertions(+), 14 deletions(-)
drivers/gpu/drm/i915/display/intel_bw.c +117 -1
@@ -6,8 +6,10 @@#include <drm/drm_atomic_state_helper.h> #include "intel_bw.h" +#include "intel_pm.h" #include "intel_display_types.h" #include "intel_sideband.h" +#include "intel_cdclk.h" /* Parameters for Qclk Geyserville (QGV) */ struct intel_qgv_point {
@@ -333,7 +335,6 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_return data_rate; } -void intel_bw_crtc_update (struct intel_bw_state *bw_state,const struct intel_crtc_state *crtc_state) {
@@ -410,6 +411,121 @@ intel_atomic_get_bw_state(struct intel_atomic_state *state)return to_intel_bw_state (bw_state); } +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +struct drm_i915_private *dev_priv =to_i915 (state->base.dev); +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int max_bw =0 ; +int slice_id; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +enum plane_id plane_id; +struct intel_dbuf_bw *crtc_bw; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + crtc_bw = &new_bw_state->dbuf_bw[crtc->pipe]; + +memset (&crtc_bw->used_bw,0 ,sizeof (crtc_bw->used_bw)); + +for_each_plane_id_on_crtc (crtc, plane_id) { +const struct skl_ddb_entry *plane_alloc = + &crtc_state->wm.skl.plane_ddb_y[plane_id]; +const struct skl_ddb_entry *uv_plane_alloc = + &crtc_state->wm.skl.plane_ddb_uv[plane_id]; +unsigned int data_rate = crtc_state->data_rate[plane_id]; +unsigned int dbuf_mask =0 ; + + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, plane_alloc); + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, uv_plane_alloc); + +/* +* FIXME: To calculate that more properly we probably need to +* to split per plane data_rate into data_rate_y and data_rate_uv +* for multiplanar formats in order not to get accounted those twice +* if they happen to reside on different slices. +* However for pre-icl this would work anyway because we have only single +* slice and for icl+ uv plane has non-zero data rate. +* So in worst case those calculation are a bit pessimistic, which +* shouldn't pose any significant problem anyway. +*/ +for_each_dbuf_slice_in_mask (slice_id, dbuf_mask) + crtc_bw->used_bw[slice_id] += data_rate; + } + +for_each_dbuf_slice (slice_id) { +/* +* Current experimental observations show that contrary to BSpec +* we get underruns once we exceed 64 * CDCLK for slices in total. +* As a temporary measure in order not to keep CDCLK bumped up all the +* time we calculate CDCLK according to this formula for overall bw +* consumed by slices. +*/ + max_bw += crtc_bw->used_bw[slice_id]; + } + + new_bw_state->min_cdclk = max_bw /64 ; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); +if (ret) +return ret; + } + +return 0 ; +} + +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int min_cdclk =0 ; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_cdclk_state *cdclk_state; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + cdclk_state =intel_atomic_get_cdclk_state (state); +if (IS_ERR (cdclk_state)) +return PTR_ERR (cdclk_state); + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + new_bw_state->min_cdclk = min_cdclk; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); +if (ret) +return ret; + } + +return 0 ; +} +int intel_bw_atomic_check (struct intel_atomic_state *state) {struct drm_i915_private *dev_priv =to_i915 (state->base.dev);
drivers/gpu/drm/i915/display/intel_bw.h +10 -0
@@ -10,13 +10,19 @@#include "intel_display.h" #include "intel_global_state.h" +#include "intel_display_power.h" struct drm_i915_private ;struct intel_atomic_state ;struct intel_crtc_state ; +struct intel_dbuf_bw { +int used_bw[I915_MAX_DBUF_SLICES ]; +}; +struct intel_bw_state {struct intel_global_state base; +struct intel_dbuf_bw dbuf_bw[I915_MAX_PIPES ];/* * Contains a bit mask, used to determine, whether correspondent
@@ -29,6 +35,8 @@ struct intel_bw_state {/* bitmask of active pipes */ u8 active_pipes; + +int min_cdclk; };#define to_intel_bw_state (x) container_of((x), struct intel_bw_state, base)
@@ -47,5 +55,7 @@ int intel_bw_init(struct drm_i915_private *dev_priv);int intel_bw_atomic_check (struct intel_atomic_state *state);void intel_bw_crtc_update (struct intel_bw_state *bw_state,const struct intel_crtc_state *crtc_state); +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state); +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state);#endif /* __INTEL_BW_H__ */
drivers/gpu/drm/i915/display/intel_cdclk.c +24 -4
@@ -21,10 +21,12 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/time.h> #include "intel_atomic.h" #include "intel_cdclk.h" #include "intel_display_types.h" #include "intel_sideband.h" +#include "intel_bw.h" /** * DOC: CDCLK / RAWCLK
@@ -2093,11 +2095,9 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)static int intel_compute_min_cdclk (struct intel_cdclk_state *cdclk_state) {struct intel_atomic_state *state = cdclk_state->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->base.dev);struct intel_crtc *crtc;struct intel_crtc_state *crtc_state;int min_cdclk, i; -enum pipe pipe;for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) {int ret;
@@ -2117,8 +2117,18 @@ static int intel_compute_min_cdclk(struct intel_cdclk_state *cdclk_state) } min_cdclk = cdclk_state->force_min_cdclk; -for_each_pipe (dev_priv, pipe) - min_cdclk =max (cdclk_state->min_cdclk[pipe], min_cdclk); + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_bw_state *bw_state; + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + + min_cdclk =max (bw_state->min_cdclk, min_cdclk); + }return min_cdclk; }
@@ -2760,25 +2770,30 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv) {if (INTEL_GEN (dev_priv) >=12 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = tgl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_ELKHARTLAKE (dev_priv)) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = ehl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (INTEL_GEN (dev_priv) >=11 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = icl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_CANNONLAKE (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = cnl_calc_voltage_level; dev_priv->cdclk.table = cnl_cdclk_table; }else if (IS_GEN9_LP (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = bxt_calc_voltage_level;
@@ -2787,18 +2802,23 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv)else dev_priv->cdclk.table = bxt_cdclk_table; }else if (IS_GEN9_BC (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = skl_set_cdclk; dev_priv->display.modeset_calc_cdclk = skl_modeset_calc_cdclk; }else if (IS_BROADWELL (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bdw_set_cdclk; dev_priv->display.modeset_calc_cdclk = bdw_modeset_calc_cdclk; }else if (IS_CHERRYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = chv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else if (IS_VALLEYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = vlv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = fixed_modeset_calc_cdclk; }
drivers/gpu/drm/i915/display/intel_cdclk.h +0 -1
@@ -7,7 +7,6 @@#define __INTEL_CDCLK_H__#include <linux/types.h> -#include "i915_drv.h" #include "intel_display.h" #include "intel_global_state.h"
drivers/gpu/drm/i915/display/intel_display.c +33 -6
@@ -14634,16 +14634,14 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state)static int intel_atomic_check_cdclk (struct intel_atomic_state *state,bool *need_cdclk_calc) { -struct intel_cdclk_state *new_cdclk_state; +struct drm_i915_private *dev_priv =to_i915 (state->base.dev);int i;struct intel_plane_state *plane_state;struct intel_plane *plane;int ret; - - new_cdclk_state =intel_atomic_get_new_cdclk_state (state); -if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) - *need_cdclk_calc = true; - +struct intel_cdclk_state *new_cdclk_state; +struct intel_crtc_state *new_crtc_state; +struct intel_crtc *crtc;/* * active_planes bitmask has been updated, and potentially * affected planes are part of the state. We can now
@@ -14655,6 +14653,35 @@ static int intel_atomic_check_cdclk(struct intel_atomic_state *state,return ret; } + new_cdclk_state =intel_atomic_get_new_cdclk_state (state); + +if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) + *need_cdclk_calc = true; + + ret = dev_priv->display.bw_calc_min_cdclk (state); +if (ret) +return ret; + +if (!new_cdclk_state) +return 0 ; + +for_each_new_intel_crtc_in_state (state, crtc, new_crtc_state, i) { +struct intel_bw_state *bw_state; +int min_cdclk =0 ; + + min_cdclk =max (new_cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + +/* +* Currently do this change only if we need to increase +*/ +if (bw_state->min_cdclk > min_cdclk) + *need_cdclk_calc = true; + } +return 0 ; }
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -273,6 +273,7 @@ struct drm_i915_display_funcs {void (*set_cdclk)(struct drm_i915_private *dev_priv,const struct intel_cdclk_config *cdclk_config,enum pipe pipe); +int (*bw_calc_min_cdclk)(struct intel_atomic_state *state);int (*get_fifo_size)(struct drm_i915_private *dev_priv,enum i9xx_plane_id i9xx_plane);int (*compute_pipe_wm)(struct intel_crtc_state *crtc_state);
drivers/gpu/drm/i915/intel_pm.c +29 -2
@@ -3939,10 +3939,9 @@ icl_get_first_dbuf_slice_offset(u32 dbuf_slice_mask,return offset; } -static u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) {u16 ddb_size =INTEL_INFO (dev_priv)->ddb_size; -drm_WARN_ON (&dev_priv->drm, ddb_size ==0 );if (INTEL_GEN (dev_priv) <11 )
@@ -3951,6 +3950,34 @@ static u16 intel_get_ddb_size(struct drm_i915_private *dev_priv)return ddb_size; } +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry) +{ +u32 slice_mask =0 ; +u16 ddb_size =intel_get_ddb_size (dev_priv); +u16 num_supported_slices =INTEL_INFO (dev_priv)->num_supported_dbuf_slices; +u16 slice_size = ddb_size / num_supported_slices; +u16 start_slice; +u16 end_slice; + +if (!skl_ddb_entry_size (entry)) +return 0 ; + + start_slice = entry->start / slice_size; + end_slice = (entry->end -1 ) / slice_size; + +/* +* Per plane DDB entry can in a really worst case be on multiple slices +* but single entry is anyway contigious. +*/ +while (start_slice <= end_slice) { + slice_mask |=BIT (start_slice); + start_slice++; + } + +return slice_mask; +} +static u8 skl_compute_dbuf_slices (const struct intel_crtc_state *crtc_state,u8 active_pipes);
drivers/gpu/drm/i915/intel_pm.h +3 -0
@@ -38,6 +38,9 @@ void skl_pipe_ddb_get_hw_state(struct intel_crtc *crtc,struct skl_ddb_entry *ddb_y, struct skl_ddb_entry *ddb_uv);void skl_ddb_get_hw_state (struct drm_i915_private *dev_priv); +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv); +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry);void skl_pipe_wm_get_hw_state (struct intel_crtc *crtc,struct skl_pipe_wm *out);void g4x_wm_sanitize (struct drm_i915_private *dev_priv);
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 6/7 drm/i915: Adjust CDCLK accordingly to our DBuf bw needs
According to BSpec max BW per slice is calculated using formula Max BW = CDCLK * 64. Currently when calculating min CDCLK we account only per plane requirements, however in order to avoid FIFO underruns we need to estimate accumulated BW consumed by all planes(ddb entries basically) residing on that particular DBuf slice. This will allow us to put CDCLK lower and save power when we don't need that much bandwidth or gain additional performance once plane consumption grows.
v2: - Fix long line warning
- Limited new DBuf bw checks to only gens >= 11
v3: - Lets track used Dbuf bw per slice and per crtc in bw state
(or may be in DBuf state in future), that way we don't need to have all crtcs in state and those only if we detect if are actually going to change cdclk, just same way as we do with other stuff, i.e intel_atomic_serialize_global_state and co. Just as per Ville's paradigm.
- Made dbuf bw calculation procedure look nicer by introducing for_each_dbuf_slice_in_mask - we often will now need to iterate slices using mask.
- According to experimental results CDCLK * 64 accounts for overall bandwidth across all dbufs, not per dbuf.
v4: - Fixed missing const(Ville)
- Removed spurious whitespaces(Ville)
- Fixed local variable init(reduced scope where not needed)
- Added some comments about data rate for planar formats
- Changed struct intel_crtc_bw to intel_dbuf_bw
- Moved dbuf bw calculation to intel_compute_min_cdclk(Ville)
v5: - Removed unneeded macro
v6: - Prevent too frequent CDCLK switching back and forth:
Always switch to higher CDCLK when needed to prevent bandwidth issues, however don't switch to lower CDCLK earlier than once in 30 minutes in order to prevent constant modeset blinking. We could of course not switch back at all, however this is bad from power consumption point of view.
v7: - Fixed to track cdclk using bw_state, modeset will be now
triggered only when CDCLK change is really needed.
v8: - Lock global state if bw_state->min_cdclk is changed.
- Try getting bw_state only if there are crtcs in the commit (need to have read-locked global state)
v9: - Do not do Dbuf bw check for gens < 9 - triggers WARN
as ddb_size is 0.
v10: - Lock global state for older gens as well.
v11: - Define new bw_calc_min_cdclk hook, instead of using
a condition(Manasi Navare)
v12: - Fixed rebase conflict
--- drivers/gpu/drm/i915/display/intel_bw.c | 119 ++++++++++++++++++- drivers/gpu/drm/i915/display/intel_bw.h | 10 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 28 ++++- drivers/gpu/drm/i915/display/intel_cdclk.h | 1 - drivers/gpu/drm/i915/display/intel_display.c | 39 +++++- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 31 ++++- drivers/gpu/drm/i915/intel_pm.h | 4 + 8 files changed, 218 insertions(+), 15 deletions(-)
drivers/gpu/drm/i915/display/intel_bw.c +117 -2
@@ -6,11 +6,12 @@#include <drm/drm_atomic_state_helper.h> #include "intel_bw.h" +#include "intel_pm.h" #include "intel_display_types.h" #include "intel_sideband.h" #include "intel_atomic.h" #include "intel_pm.h" - +#include "intel_cdclk.h" /* Parameters for Qclk Geyserville (QGV) */ struct intel_qgv_point {
@@ -343,7 +344,6 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_return data_rate; } -void intel_bw_crtc_update (struct intel_bw_state *bw_state,const struct intel_crtc_state *crtc_state) {
@@ -420,6 +420,121 @@ intel_atomic_get_bw_state(struct intel_atomic_state *state)return to_intel_bw_state (bw_state); } +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +struct drm_i915_private *dev_priv =to_i915 (state->base.dev); +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int max_bw =0 ; +int slice_id; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +enum plane_id plane_id; +struct intel_dbuf_bw *crtc_bw; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + crtc_bw = &new_bw_state->dbuf_bw[crtc->pipe]; + +memset (&crtc_bw->used_bw,0 ,sizeof (crtc_bw->used_bw)); + +for_each_plane_id_on_crtc (crtc, plane_id) { +const struct skl_ddb_entry *plane_alloc = + &crtc_state->wm.skl.plane_ddb_y[plane_id]; +const struct skl_ddb_entry *uv_plane_alloc = + &crtc_state->wm.skl.plane_ddb_uv[plane_id]; +unsigned int data_rate = crtc_state->data_rate[plane_id]; +unsigned int dbuf_mask =0 ; + + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, plane_alloc); + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, uv_plane_alloc); + +/* +* FIXME: To calculate that more properly we probably need to +* to split per plane data_rate into data_rate_y and data_rate_uv +* for multiplanar formats in order not to get accounted those twice +* if they happen to reside on different slices. +* However for pre-icl this would work anyway because we have only single +* slice and for icl+ uv plane has non-zero data rate. +* So in worst case those calculation are a bit pessimistic, which +* shouldn't pose any significant problem anyway. +*/ +for_each_dbuf_slice_in_mask (slice_id, dbuf_mask) + crtc_bw->used_bw[slice_id] += data_rate; + } + +for_each_dbuf_slice (slice_id) { +/* +* Current experimental observations show that contrary to BSpec +* we get underruns once we exceed 64 * CDCLK for slices in total. +* As a temporary measure in order not to keep CDCLK bumped up all the +* time we calculate CDCLK according to this formula for overall bw +* consumed by slices. +*/ + max_bw += crtc_bw->used_bw[slice_id]; + } + + new_bw_state->min_cdclk = max_bw /64 ; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); +if (ret) +return ret; + } + +return 0 ; +} + +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int min_cdclk =0 ; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_cdclk_state *cdclk_state; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + cdclk_state =intel_atomic_get_cdclk_state (state); +if (IS_ERR (cdclk_state)) +return PTR_ERR (cdclk_state); + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + new_bw_state->min_cdclk = min_cdclk; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); +if (ret) +return ret; + } + +return 0 ; +} +int intel_bw_atomic_check (struct intel_atomic_state *state) {struct drm_i915_private *dev_priv =to_i915 (state->base.dev);
drivers/gpu/drm/i915/display/intel_bw.h +10 -0
@@ -10,13 +10,19 @@#include "intel_display.h" #include "intel_global_state.h" +#include "intel_display_power.h" struct drm_i915_private ;struct intel_atomic_state ;struct intel_crtc_state ; +struct intel_dbuf_bw { +int used_bw[I915_MAX_DBUF_SLICES ]; +}; +struct intel_bw_state {struct intel_global_state base; +struct intel_dbuf_bw dbuf_bw[I915_MAX_PIPES ];/* * Contains a bit mask, used to determine, whether correspondent
@@ -36,6 +42,8 @@ struct intel_bw_state {/* bitmask of active pipes */ u8 active_pipes; + +int min_cdclk; };#define to_intel_bw_state (x) container_of((x), struct intel_bw_state, base)
@@ -56,5 +64,7 @@ void intel_bw_crtc_update(struct intel_bw_state *bw_state, const struct intel_crtc_state *crtc_state);int icl_pcode_restrict_qgv_points (struct drm_i915_private *dev_priv,u32 points_mask); +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state); +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state);#endif /* __INTEL_BW_H__ */
drivers/gpu/drm/i915/display/intel_cdclk.c +24 -4
@@ -21,10 +21,12 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/time.h> #include "intel_atomic.h" #include "intel_cdclk.h" #include "intel_display_types.h" #include "intel_sideband.h" +#include "intel_bw.h" /** * DOC: CDCLK / RAWCLK
@@ -2093,11 +2095,9 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)static int intel_compute_min_cdclk (struct intel_cdclk_state *cdclk_state) {struct intel_atomic_state *state = cdclk_state->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->base.dev);struct intel_crtc *crtc;struct intel_crtc_state *crtc_state;int min_cdclk, i; -enum pipe pipe;for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) {int ret;
@@ -2117,8 +2117,18 @@ static int intel_compute_min_cdclk(struct intel_cdclk_state *cdclk_state) } min_cdclk = cdclk_state->force_min_cdclk; -for_each_pipe (dev_priv, pipe) - min_cdclk =max (cdclk_state->min_cdclk[pipe], min_cdclk); + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_bw_state *bw_state; + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + + min_cdclk =max (bw_state->min_cdclk, min_cdclk); + }return min_cdclk; }
@@ -2790,25 +2800,30 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv) {if (INTEL_GEN (dev_priv) >=12 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = tgl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_ELKHARTLAKE (dev_priv)) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = ehl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (INTEL_GEN (dev_priv) >=11 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = icl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_CANNONLAKE (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = cnl_calc_voltage_level; dev_priv->cdclk.table = cnl_cdclk_table; }else if (IS_GEN9_LP (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = bxt_calc_voltage_level;
@@ -2817,18 +2832,23 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv)else dev_priv->cdclk.table = bxt_cdclk_table; }else if (IS_GEN9_BC (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = skl_set_cdclk; dev_priv->display.modeset_calc_cdclk = skl_modeset_calc_cdclk; }else if (IS_BROADWELL (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bdw_set_cdclk; dev_priv->display.modeset_calc_cdclk = bdw_modeset_calc_cdclk; }else if (IS_CHERRYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = chv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else if (IS_VALLEYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = vlv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = fixed_modeset_calc_cdclk; }
drivers/gpu/drm/i915/display/intel_cdclk.h +0 -1
@@ -7,7 +7,6 @@#define __INTEL_CDCLK_H__#include <linux/types.h> -#include "i915_drv.h" #include "intel_display.h" #include "intel_global_state.h"
drivers/gpu/drm/i915/display/intel_display.c +33 -6
@@ -14703,16 +14703,14 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state)static int intel_atomic_check_cdclk (struct intel_atomic_state *state,bool *need_cdclk_calc) { -struct intel_cdclk_state *new_cdclk_state; +struct drm_i915_private *dev_priv =to_i915 (state->base.dev);int i;struct intel_plane_state *plane_state;struct intel_plane *plane;int ret; - - new_cdclk_state =intel_atomic_get_new_cdclk_state (state); -if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) - *need_cdclk_calc = true; - +struct intel_cdclk_state *new_cdclk_state; +struct intel_crtc_state *new_crtc_state; +struct intel_crtc *crtc;/* * active_planes bitmask has been updated, and potentially * affected planes are part of the state. We can now
@@ -14724,6 +14722,35 @@ static int intel_atomic_check_cdclk(struct intel_atomic_state *state,return ret; } + new_cdclk_state =intel_atomic_get_new_cdclk_state (state); + +if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) + *need_cdclk_calc = true; + + ret = dev_priv->display.bw_calc_min_cdclk (state); +if (ret) +return ret; + +if (!new_cdclk_state) +return 0 ; + +for_each_new_intel_crtc_in_state (state, crtc, new_crtc_state, i) { +struct intel_bw_state *bw_state; +int min_cdclk =0 ; + + min_cdclk =max (new_cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + +/* +* Currently do this change only if we need to increase +*/ +if (bw_state->min_cdclk > min_cdclk) + *need_cdclk_calc = true; + } +return 0 ; }
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -273,6 +273,7 @@ struct drm_i915_display_funcs {void (*set_cdclk)(struct drm_i915_private *dev_priv,const struct intel_cdclk_config *cdclk_config,enum pipe pipe); +int (*bw_calc_min_cdclk)(struct intel_atomic_state *state);int (*get_fifo_size)(struct drm_i915_private *dev_priv,enum i9xx_plane_id i9xx_plane);int (*compute_pipe_wm)(struct intel_crtc_state *crtc_state);
drivers/gpu/drm/i915/intel_pm.c +29 -2
@@ -4031,10 +4031,9 @@ icl_get_first_dbuf_slice_offset(u32 dbuf_slice_mask,return offset; } -static u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) {u16 ddb_size =INTEL_INFO (dev_priv)->ddb_size; -drm_WARN_ON (&dev_priv->drm, ddb_size ==0 );if (INTEL_GEN (dev_priv) <11 )
@@ -4043,6 +4042,34 @@ static u16 intel_get_ddb_size(struct drm_i915_private *dev_priv)return ddb_size; } +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry) +{ +u32 slice_mask =0 ; +u16 ddb_size =intel_get_ddb_size (dev_priv); +u16 num_supported_slices =INTEL_INFO (dev_priv)->num_supported_dbuf_slices; +u16 slice_size = ddb_size / num_supported_slices; +u16 start_slice; +u16 end_slice; + +if (!skl_ddb_entry_size (entry)) +return 0 ; + + start_slice = entry->start / slice_size; + end_slice = (entry->end -1 ) / slice_size; + +/* +* Per plane DDB entry can in a really worst case be on multiple slices +* but single entry is anyway contigious. +*/ +while (start_slice <= end_slice) { + slice_mask |=BIT (start_slice); + start_slice++; + } + +return slice_mask; +} +static u8 skl_compute_dbuf_slices (const struct intel_crtc_state *crtc_state,u8 active_pipes);
drivers/gpu/drm/i915/intel_pm.h +4 -0
@@ -39,6 +39,10 @@ u8 intel_enabled_dbuf_slices_mask(struct drm_i915_private *dev_priv);void skl_pipe_ddb_get_hw_state (struct intel_crtc *crtc,struct skl_ddb_entry *ddb_y,struct skl_ddb_entry *ddb_uv); +void skl_ddb_get_hw_state (struct drm_i915_private *dev_priv); +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv); +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry);void skl_pipe_wm_get_hw_state (struct intel_crtc *crtc,struct skl_pipe_wm *out);void g4x_wm_sanitize (struct drm_i915_private *dev_priv);
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] [PATCH v9 6/7] drm/i915: Adjust CDCLK accordingly to our DBuf bw needs
Quoted 50 lines · Stanislav Lisovskiy
According to BSpec max BW per slice is calculated using formula Max BW = CDCLK * 64. Currently when calculating min CDCLK we account only per plane requirements, however in order to avoid FIFO underruns we need to estimate accumulated BW consumed by all planes(ddb entries basically) residing on that particular DBuf slice. This will allow us to put CDCLK lower and save power when we don't need that much bandwidth or gain additional performance once plane consumption grows.
v2: - Fix long line warning
- Limited new DBuf bw checks to only gens >= 11v3: - Lets track used Dbuf bw per slice and per crtc in bw state
(or may be in DBuf state in future), that way we don't need to have all crtcs in state and those only if we detect if are actually going to change cdclk, just same way as we do with other stuff, i.eintel_atomic_serialize_global_stateand co. Just as per Ville's paradigm.
- Made dbuf bw calculation procedure look nicer by introducingfor_each_dbuf_slice_in_mask- we often will now need to iterate slices using mask.
- According to experimental results CDCLK * 64 accounts for overall bandwidth across all dbufs, not per dbuf.v4: - Fixed missing const(Ville)
- Removed spurious whitespaces(Ville)
- Fixed local variable init(reduced scope where not needed)
- Added some comments about data rate for planar formats
- Changed structintel_crtc_bwtointel_dbuf_bw
- Moved dbuf bw calculation tointel_compute_min_cdclk(Ville)v5: - Removed unneeded macro
v6: - Prevent too frequent CDCLK switching back and forth:
Always switch to higher CDCLK when needed to prevent bandwidth issues, however don't switch to lower CDCLK earlier than once in 30 minutes in order to prevent constant modeset blinking. We could of course not switch back at all, however this is bad from power consumption point of view.v7: - Fixed to track cdclk using
bw_state, modeset will be now
triggered only when CDCLK change is really needed.v8: - Lock global state if
bw_state->min_cdclkis changed.
- Try gettingbw_stateonly if there are crtcs in the commit (need to have read-locked global state)v9: - Do not do Dbuf bw check for gens < 9 - triggers WARN
asddb_sizeis 0.
Quoted 8 lines
v10: - Lock global state for older gens as well.
v11: - Define new
bw_calc_min_cdclkhook, instead of using
a condition(Manasi Navare)v12: - Fixed rebase conflict
Signed-off-by Stanislav Lisovskiy <[email protected]>
Looks good now with the hooks
Manasi
Quoted 459 lines
--- drivers/gpu/drm/i915/display/intel_bw.c | 119 ++++++++++++++++++- drivers/gpu/drm/i915/display/intel_bw.h | 10 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 28 ++++- drivers/gpu/drm/i915/display/intel_cdclk.h | 1 - drivers/gpu/drm/i915/display/intel_display.c | 39 +++++- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 31 ++++- drivers/gpu/drm/i915/intel_pm.h | 4 + 8 files changed, 218 insertions(+), 15 deletions(-)drivers/gpu/drm/i915/display/intel_bw.c +117
-2@@ -6,11 +6,12 @@#include <drm/drm_atomic_state_helper.h> #include "intel_bw.h" +#include "intel_pm.h" #include "intel_display_types.h" #include "intel_sideband.h" #include "intel_atomic.h" #include "intel_pm.h" - +#include "intel_cdclk.h" /* Parameters for Qclk Geyserville (QGV) */ struct intel_qgv_point {@@ -343,7 +344,6 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_return data_rate; } -void intel_bw_crtc_update (struct intel_bw_state *bw_state,const struct intel_crtc_state *crtc_state) {@@ -420,6 +420,121 @@ intel_atomic_get_bw_state(struct intel_atomic_state *state)return to_intel_bw_state (bw_state); } +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +struct drm_i915_private *dev_priv =to_i915 (state->base.dev); +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int max_bw =0 ; +int slice_id; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +enum plane_id plane_id; +struct intel_dbuf_bw *crtc_bw; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + crtc_bw = &new_bw_state->dbuf_bw[crtc->pipe]; + +memset (&crtc_bw->used_bw,0 ,sizeof (crtc_bw->used_bw)); + +for_each_plane_id_on_crtc (crtc, plane_id) { +const struct skl_ddb_entry *plane_alloc = + &crtc_state->wm.skl.plane_ddb_y[plane_id]; +const struct skl_ddb_entry *uv_plane_alloc = + &crtc_state->wm.skl.plane_ddb_uv[plane_id]; +unsigned int data_rate = crtc_state->data_rate[plane_id]; +unsigned int dbuf_mask =0 ; + + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, plane_alloc); + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, uv_plane_alloc); + +/* +* FIXME: To calculate that more properly we probably need to +* to split per plane data_rate into data_rate_y and data_rate_uv +* for multiplanar formats in order not to get accounted those twice +* if they happen to reside on different slices. +* However for pre-icl this would work anyway because we have only single +* slice and for icl+ uv plane has non-zero data rate. +* So in worst case those calculation are a bit pessimistic, which +* shouldn't pose any significant problem anyway. +*/ +for_each_dbuf_slice_in_mask (slice_id, dbuf_mask) + crtc_bw->used_bw[slice_id] += data_rate; + } + +for_each_dbuf_slice (slice_id) { +/* +* Current experimental observations show that contrary to BSpec +* we get underruns once we exceed 64 * CDCLK for slices in total. +* As a temporary measure in order not to keep CDCLK bumped up all the +* time we calculate CDCLK according to this formula for overall bw +* consumed by slices. +*/ + max_bw += crtc_bw->used_bw[slice_id]; + } + + new_bw_state->min_cdclk = max_bw /64 ; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); +if (ret) +return ret; + } + +return 0 ; +} + +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int min_cdclk =0 ; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_cdclk_state *cdclk_state; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + cdclk_state =intel_atomic_get_cdclk_state (state); +if (IS_ERR (cdclk_state)) +return PTR_ERR (cdclk_state); + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + new_bw_state->min_cdclk = min_cdclk; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); +if (ret) +return ret; + } + +return 0 ; +} +int intel_bw_atomic_check (struct intel_atomic_state *state) {struct drm_i915_private *dev_priv =to_i915 (state->base.dev);drivers/gpu/drm/i915/display/intel_bw.h +10
-0@@ -10,13 +10,19 @@#include "intel_display.h" #include "intel_global_state.h" +#include "intel_display_power.h" struct drm_i915_private ;struct intel_atomic_state ;struct intel_crtc_state ; +struct intel_dbuf_bw { +int used_bw[I915_MAX_DBUF_SLICES ]; +}; +struct intel_bw_state {struct intel_global_state base; +struct intel_dbuf_bw dbuf_bw[I915_MAX_PIPES ];/* * Contains a bit mask, used to determine, whether correspondent @@ -36,6 +42,8 @@ struct intel_bw_state {/* bitmask of active pipes */ u8 active_pipes; + +int min_cdclk; };#define to_intel_bw_state (x) container_of((x), struct intel_bw_state, base)@@ -56,5 +64,7 @@ void intel_bw_crtc_update(struct intel_bw_state *bw_state, const struct intel_crtc_state *crtc_state);int icl_pcode_restrict_qgv_points (struct drm_i915_private *dev_priv,u32 points_mask); +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state); +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state);#endif /* __INTEL_BW_H__ */ drivers/gpu/drm/i915/display/intel_cdclk.c +24
-4@@ -21,10 +21,12 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/time.h> #include "intel_atomic.h" #include "intel_cdclk.h" #include "intel_display_types.h" #include "intel_sideband.h" +#include "intel_bw.h" /** * DOC: CDCLK / RAWCLK @@ -2093,11 +2095,9 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)static int intel_compute_min_cdclk (struct intel_cdclk_state *cdclk_state) {struct intel_atomic_state *state = cdclk_state->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->base.dev);struct intel_crtc *crtc;struct intel_crtc_state *crtc_state;int min_cdclk, i; -enum pipe pipe;for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) {int ret;@@ -2117,8 +2117,18 @@ static int intel_compute_min_cdclk(struct intel_cdclk_state *cdclk_state) } min_cdclk = cdclk_state->force_min_cdclk; -for_each_pipe (dev_priv, pipe) - min_cdclk =max (cdclk_state->min_cdclk[pipe], min_cdclk); + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_bw_state *bw_state; + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + + min_cdclk =max (bw_state->min_cdclk, min_cdclk); + }return min_cdclk; }@@ -2790,25 +2800,30 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv) {if (INTEL_GEN (dev_priv) >=12 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = tgl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_ELKHARTLAKE (dev_priv)) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = ehl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (INTEL_GEN (dev_priv) >=11 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = icl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_CANNONLAKE (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = cnl_calc_voltage_level; dev_priv->cdclk.table = cnl_cdclk_table; }else if (IS_GEN9_LP (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = bxt_calc_voltage_level;@@ -2817,18 +2832,23 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv)else dev_priv->cdclk.table = bxt_cdclk_table; }else if (IS_GEN9_BC (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = skl_set_cdclk; dev_priv->display.modeset_calc_cdclk = skl_modeset_calc_cdclk; }else if (IS_BROADWELL (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bdw_set_cdclk; dev_priv->display.modeset_calc_cdclk = bdw_modeset_calc_cdclk; }else if (IS_CHERRYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = chv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else if (IS_VALLEYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = vlv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = fixed_modeset_calc_cdclk; }drivers/gpu/drm/i915/display/intel_cdclk.h +0
-1@@ -7,7 +7,6 @@#define __INTEL_CDCLK_H__#include <linux/types.h> -#include "i915_drv.h" #include "intel_display.h" #include "intel_global_state.h" drivers/gpu/drm/i915/display/intel_display.c +33
-6@@ -14703,16 +14703,14 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state)static int intel_atomic_check_cdclk (struct intel_atomic_state *state,bool *need_cdclk_calc) { -struct intel_cdclk_state *new_cdclk_state; +struct drm_i915_private *dev_priv =to_i915 (state->base.dev);int i;struct intel_plane_state *plane_state;struct intel_plane *plane;int ret; - - new_cdclk_state =intel_atomic_get_new_cdclk_state (state); -if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) - *need_cdclk_calc = true; - +struct intel_cdclk_state *new_cdclk_state; +struct intel_crtc_state *new_crtc_state; +struct intel_crtc *crtc;/* * active_planes bitmask has been updated, and potentially * affected planes are part of the state. We can now @@ -14724,6 +14722,35 @@ static int intel_atomic_check_cdclk(struct intel_atomic_state *state,return ret; } + new_cdclk_state =intel_atomic_get_new_cdclk_state (state); + +if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) + *need_cdclk_calc = true; + + ret = dev_priv->display.bw_calc_min_cdclk (state); +if (ret) +return ret; + +if (!new_cdclk_state) +return 0 ; + +for_each_new_intel_crtc_in_state (state, crtc, new_crtc_state, i) { +struct intel_bw_state *bw_state; +int min_cdclk =0 ; + + min_cdclk =max (new_cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + +/* +* Currently do this change only if we need to increase +*/ +if (bw_state->min_cdclk > min_cdclk) + *need_cdclk_calc = true; + } +return 0 ; }drivers/gpu/drm/i915/i915_drv.h +1
-0@@ -273,6 +273,7 @@ struct drm_i915_display_funcs {void (*set_cdclk)(struct drm_i915_private *dev_priv,const struct intel_cdclk_config *cdclk_config,enum pipe pipe); +int (*bw_calc_min_cdclk)(struct intel_atomic_state *state);int (*get_fifo_size)(struct drm_i915_private *dev_priv,enum i9xx_plane_id i9xx_plane);int (*compute_pipe_wm)(struct intel_crtc_state *crtc_state);drivers/gpu/drm/i915/intel_pm.c +29
-2@@ -4031,10 +4031,9 @@ icl_get_first_dbuf_slice_offset(u32 dbuf_slice_mask,return offset; } -static u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) {u16 ddb_size =INTEL_INFO (dev_priv)->ddb_size; -drm_WARN_ON (&dev_priv->drm, ddb_size ==0 );if (INTEL_GEN (dev_priv) <11 )@@ -4043,6 +4042,34 @@ static u16 intel_get_ddb_size(struct drm_i915_private *dev_priv)return ddb_size; } +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry) +{ +u32 slice_mask =0 ; +u16 ddb_size =intel_get_ddb_size (dev_priv); +u16 num_supported_slices =INTEL_INFO (dev_priv)->num_supported_dbuf_slices; +u16 slice_size = ddb_size / num_supported_slices; +u16 start_slice; +u16 end_slice; + +if (!skl_ddb_entry_size (entry)) +return 0 ; + + start_slice = entry->start / slice_size; + end_slice = (entry->end -1 ) / slice_size; + +/* +* Per plane DDB entry can in a really worst case be on multiple slices +* but single entry is anyway contigious. +*/ +while (start_slice <= end_slice) { + slice_mask |=BIT (start_slice); + start_slice++; + } + +return slice_mask; +} +static u8 skl_compute_dbuf_slices (const struct intel_crtc_state *crtc_state,u8 active_pipes);drivers/gpu/drm/i915/intel_pm.h +4
-0@@ -39,6 +39,10 @@ u8 intel_enabled_dbuf_slices_mask(struct drm_i915_private *dev_priv);void skl_pipe_ddb_get_hw_state (struct intel_crtc *crtc,struct skl_ddb_entry *ddb_y,struct skl_ddb_entry *ddb_uv); +void skl_ddb_get_hw_state (struct drm_i915_private *dev_priv); +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv); +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry);void skl_pipe_wm_get_hw_state (struct intel_crtc *crtc,struct skl_pipe_wm *out);void g4x_wm_sanitize (struct drm_i915_private *dev_priv);Signature · 1 line
2.24.1.485.gad05a3d8e5
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 6/7 drm/i915: Adjust CDCLK accordingly to our DBuf bw needs
In reply to Stanislav LisovskiyAccording to BSpec max BW per slice is calculated using formula Max BW = CDCLK * 64. Currently when calculating min CDCLK we account only per plane requirements, however in order to avoid FIFO underruns we need to estimate accumulated BW consumed by all planes(ddb entries basically) residing on that particular DBuf slice. This will allow us to put CDCLK lower and save power when we don't need that much bandwidth or gain additional performance once plane consumption grows.
v2: - Fix long line warning
- Limited new DBuf bw checks to only gens >= 11
v3: - Lets track used Dbuf bw per slice and per crtc in bw state
(or may be in DBuf state in future), that way we don't need to have all crtcs in state and those only if we detect if are actually going to change cdclk, just same way as we do with other stuff, i.e intel_atomic_serialize_global_state and co. Just as per Ville's paradigm.
- Made dbuf bw calculation procedure look nicer by introducing for_each_dbuf_slice_in_mask - we often will now need to iterate slices using mask.
- According to experimental results CDCLK * 64 accounts for overall bandwidth across all dbufs, not per dbuf.
v4: - Fixed missing const(Ville)
- Removed spurious whitespaces(Ville)
- Fixed local variable init(reduced scope where not needed)
- Added some comments about data rate for planar formats
- Changed struct intel_crtc_bw to intel_dbuf_bw
- Moved dbuf bw calculation to intel_compute_min_cdclk(Ville)
v5: - Removed unneeded macro
v6: - Prevent too frequent CDCLK switching back and forth:
Always switch to higher CDCLK when needed to prevent bandwidth issues, however don't switch to lower CDCLK earlier than once in 30 minutes in order to prevent constant modeset blinking. We could of course not switch back at all, however this is bad from power consumption point of view.
v7: - Fixed to track cdclk using bw_state, modeset will be now
triggered only when CDCLK change is really needed.
v8: - Lock global state if bw_state->min_cdclk is changed.
- Try getting bw_state only if there are crtcs in the commit (need to have read-locked global state)
v9: - Do not do Dbuf bw check for gens < 9 - triggers WARN
as ddb_size is 0.
v10: - Lock global state for older gens as well.
v11: - Define new bw_calc_min_cdclk hook, instead of using
a condition(Manasi Navare)
v12: - Fixed rebase conflict
v13: - Added spaces after declarations to make checkpatch happy.
--- drivers/gpu/drm/i915/display/intel_bw.c | 121 ++++++++++++++++++- drivers/gpu/drm/i915/display/intel_bw.h | 10 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 28 ++++- drivers/gpu/drm/i915/display/intel_cdclk.h | 1 - drivers/gpu/drm/i915/display/intel_display.c | 39 +++++- drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 31 ++++- drivers/gpu/drm/i915/intel_pm.h | 4 + 8 files changed, 220 insertions(+), 15 deletions(-)
drivers/gpu/drm/i915/display/intel_bw.c +119 -2
@@ -6,11 +6,12 @@#include <drm/drm_atomic_state_helper.h> #include "intel_bw.h" +#include "intel_pm.h" #include "intel_display_types.h" #include "intel_sideband.h" #include "intel_atomic.h" #include "intel_pm.h" - +#include "intel_cdclk.h" /* Parameters for Qclk Geyserville (QGV) */ struct intel_qgv_point {
@@ -343,7 +344,6 @@ static unsigned int intel_bw_crtc_data_rate(const struct intel_crtc_state *crtc_return data_rate; } -void intel_bw_crtc_update (struct intel_bw_state *bw_state,const struct intel_crtc_state *crtc_state) {
@@ -420,6 +420,123 @@ intel_atomic_get_bw_state(struct intel_atomic_state *state)return to_intel_bw_state (bw_state); } +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +struct drm_i915_private *dev_priv =to_i915 (state->base.dev); +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int max_bw =0 ; +int slice_id; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +enum plane_id plane_id; +struct intel_dbuf_bw *crtc_bw; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + crtc_bw = &new_bw_state->dbuf_bw[crtc->pipe]; + +memset (&crtc_bw->used_bw,0 ,sizeof (crtc_bw->used_bw)); + +for_each_plane_id_on_crtc (crtc, plane_id) { +const struct skl_ddb_entry *plane_alloc = + &crtc_state->wm.skl.plane_ddb_y[plane_id]; +const struct skl_ddb_entry *uv_plane_alloc = + &crtc_state->wm.skl.plane_ddb_uv[plane_id]; +unsigned int data_rate = crtc_state->data_rate[plane_id]; +unsigned int dbuf_mask =0 ; + + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, plane_alloc); + dbuf_mask |=skl_ddb_dbuf_slice_mask (dev_priv, uv_plane_alloc); + +/* +* FIXME: To calculate that more properly we probably need to +* to split per plane data_rate into data_rate_y and data_rate_uv +* for multiplanar formats in order not to get accounted those twice +* if they happen to reside on different slices. +* However for pre-icl this would work anyway because we have only single +* slice and for icl+ uv plane has non-zero data rate. +* So in worst case those calculation are a bit pessimistic, which +* shouldn't pose any significant problem anyway. +*/ +for_each_dbuf_slice_in_mask (slice_id, dbuf_mask) + crtc_bw->used_bw[slice_id] += data_rate; + } + +for_each_dbuf_slice (slice_id) { +/* +* Current experimental observations show that contrary to BSpec +* we get underruns once we exceed 64 * CDCLK for slices in total. +* As a temporary measure in order not to keep CDCLK bumped up all the +* time we calculate CDCLK according to this formula for overall bw +* consumed by slices. +*/ + max_bw += crtc_bw->used_bw[slice_id]; + } + + new_bw_state->min_cdclk = max_bw /64 ; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); + +if (ret) +return ret; + } + +return 0 ; +} + +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state) +{ +int i; +const struct intel_crtc_state *crtc_state; +struct intel_crtc *crtc; +int min_cdclk =0 ; +struct intel_bw_state *new_bw_state =NULL ; +struct intel_bw_state *old_bw_state =NULL ; + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_cdclk_state *cdclk_state; + + new_bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (new_bw_state)) +return PTR_ERR (new_bw_state); + + cdclk_state =intel_atomic_get_cdclk_state (state); +if (IS_ERR (cdclk_state)) +return PTR_ERR (cdclk_state); + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + new_bw_state->min_cdclk = min_cdclk; + + old_bw_state =intel_atomic_get_old_bw_state (state); + } + +if (!old_bw_state) +return 0 ; + +if (new_bw_state->min_cdclk != old_bw_state->min_cdclk) { +int ret =intel_atomic_lock_global_state (&new_bw_state->base); + +if (ret) +return ret; + } + +return 0 ; +} +int intel_bw_atomic_check (struct intel_atomic_state *state) {struct drm_i915_private *dev_priv =to_i915 (state->base.dev);
drivers/gpu/drm/i915/display/intel_bw.h +10 -0
@@ -10,13 +10,19 @@#include "intel_display.h" #include "intel_global_state.h" +#include "intel_display_power.h" struct drm_i915_private ;struct intel_atomic_state ;struct intel_crtc_state ; +struct intel_dbuf_bw { +int used_bw[I915_MAX_DBUF_SLICES ]; +}; +struct intel_bw_state {struct intel_global_state base; +struct intel_dbuf_bw dbuf_bw[I915_MAX_PIPES ];/* * Contains a bit mask, used to determine, whether correspondent
@@ -36,6 +42,8 @@ struct intel_bw_state {/* bitmask of active pipes */ u8 active_pipes; + +int min_cdclk; };#define to_intel_bw_state (x) container_of((x), struct intel_bw_state, base)
@@ -56,5 +64,7 @@ void intel_bw_crtc_update(struct intel_bw_state *bw_state, const struct intel_crtc_state *crtc_state);int icl_pcode_restrict_qgv_points (struct drm_i915_private *dev_priv,u32 points_mask); +int intel_bw_calc_min_cdclk (struct intel_atomic_state *state); +int skl_bw_calc_min_cdclk (struct intel_atomic_state *state);#endif /* __INTEL_BW_H__ */
drivers/gpu/drm/i915/display/intel_cdclk.c +24 -4
@@ -21,10 +21,12 @@* DEALINGS IN THE SOFTWARE. */ +#include <linux/time.h> #include "intel_atomic.h" #include "intel_cdclk.h" #include "intel_display_types.h" #include "intel_sideband.h" +#include "intel_bw.h" /** * DOC: CDCLK / RAWCLK
@@ -2093,11 +2095,9 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)static int intel_compute_min_cdclk (struct intel_cdclk_state *cdclk_state) {struct intel_atomic_state *state = cdclk_state->base.state; -struct drm_i915_private *dev_priv =to_i915 (state->base.dev);struct intel_crtc *crtc;struct intel_crtc_state *crtc_state;int min_cdclk, i; -enum pipe pipe;for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) {int ret;
@@ -2117,8 +2117,18 @@ static int intel_compute_min_cdclk(struct intel_cdclk_state *cdclk_state) } min_cdclk = cdclk_state->force_min_cdclk; -for_each_pipe (dev_priv, pipe) - min_cdclk =max (cdclk_state->min_cdclk[pipe], min_cdclk); + +for_each_new_intel_crtc_in_state (state, crtc, crtc_state, i) { +struct intel_bw_state *bw_state; + + min_cdclk =max (cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + + min_cdclk =max (bw_state->min_cdclk, min_cdclk); + }return min_cdclk; }
@@ -2790,25 +2800,30 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv) {if (INTEL_GEN (dev_priv) >=12 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = tgl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_ELKHARTLAKE (dev_priv)) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = ehl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (INTEL_GEN (dev_priv) >=11 ) { dev_priv->display.set_cdclk = bxt_set_cdclk; + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = icl_calc_voltage_level; dev_priv->cdclk.table = icl_cdclk_table; }else if (IS_CANNONLAKE (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = cnl_calc_voltage_level; dev_priv->cdclk.table = cnl_cdclk_table; }else if (IS_GEN9_LP (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bxt_set_cdclk; dev_priv->display.modeset_calc_cdclk = bxt_modeset_calc_cdclk; dev_priv->display.calc_voltage_level = bxt_calc_voltage_level;
@@ -2817,18 +2832,23 @@ void intel_init_cdclk_hooks(struct drm_i915_private *dev_priv)else dev_priv->cdclk.table = bxt_cdclk_table; }else if (IS_GEN9_BC (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = skl_bw_calc_min_cdclk; dev_priv->display.set_cdclk = skl_set_cdclk; dev_priv->display.modeset_calc_cdclk = skl_modeset_calc_cdclk; }else if (IS_BROADWELL (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = bdw_set_cdclk; dev_priv->display.modeset_calc_cdclk = bdw_modeset_calc_cdclk; }else if (IS_CHERRYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = chv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else if (IS_VALLEYVIEW (dev_priv)) { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.set_cdclk = vlv_set_cdclk; dev_priv->display.modeset_calc_cdclk = vlv_modeset_calc_cdclk; }else { + dev_priv->display.bw_calc_min_cdclk = intel_bw_calc_min_cdclk; dev_priv->display.modeset_calc_cdclk = fixed_modeset_calc_cdclk; }
drivers/gpu/drm/i915/display/intel_cdclk.h +0 -1
@@ -7,7 +7,6 @@#define __INTEL_CDCLK_H__#include <linux/types.h> -#include "i915_drv.h" #include "intel_display.h" #include "intel_global_state.h"
drivers/gpu/drm/i915/display/intel_display.c +33 -6
@@ -14703,16 +14703,14 @@ static int intel_atomic_check_planes(struct intel_atomic_state *state)static int intel_atomic_check_cdclk (struct intel_atomic_state *state,bool *need_cdclk_calc) { -struct intel_cdclk_state *new_cdclk_state; +struct drm_i915_private *dev_priv =to_i915 (state->base.dev);int i;struct intel_plane_state *plane_state;struct intel_plane *plane;int ret; - - new_cdclk_state =intel_atomic_get_new_cdclk_state (state); -if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) - *need_cdclk_calc = true; - +struct intel_cdclk_state *new_cdclk_state; +struct intel_crtc_state *new_crtc_state; +struct intel_crtc *crtc;/* * active_planes bitmask has been updated, and potentially * affected planes are part of the state. We can now
@@ -14724,6 +14722,35 @@ static int intel_atomic_check_cdclk(struct intel_atomic_state *state,return ret; } + new_cdclk_state =intel_atomic_get_new_cdclk_state (state); + +if (new_cdclk_state && new_cdclk_state->force_min_cdclk_changed) + *need_cdclk_calc = true; + + ret = dev_priv->display.bw_calc_min_cdclk (state); +if (ret) +return ret; + +if (!new_cdclk_state) +return 0 ; + +for_each_new_intel_crtc_in_state (state, crtc, new_crtc_state, i) { +struct intel_bw_state *bw_state; +int min_cdclk =0 ; + + min_cdclk =max (new_cdclk_state->min_cdclk[crtc->pipe], min_cdclk); + + bw_state =intel_atomic_get_bw_state (state); +if (IS_ERR (bw_state)) +return PTR_ERR (bw_state); + +/* +* Currently do this change only if we need to increase +*/ +if (bw_state->min_cdclk > min_cdclk) + *need_cdclk_calc = true; + } +return 0 ; }
drivers/gpu/drm/i915/i915_drv.h +1 -0
@@ -273,6 +273,7 @@ struct drm_i915_display_funcs {void (*set_cdclk)(struct drm_i915_private *dev_priv,const struct intel_cdclk_config *cdclk_config,enum pipe pipe); +int (*bw_calc_min_cdclk)(struct intel_atomic_state *state);int (*get_fifo_size)(struct drm_i915_private *dev_priv,enum i9xx_plane_id i9xx_plane);int (*compute_pipe_wm)(struct intel_crtc_state *crtc_state);
drivers/gpu/drm/i915/intel_pm.c +29 -2
@@ -4031,10 +4031,9 @@ icl_get_first_dbuf_slice_offset(u32 dbuf_slice_mask,return offset; } -static u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv) {u16 ddb_size =INTEL_INFO (dev_priv)->ddb_size; -drm_WARN_ON (&dev_priv->drm, ddb_size ==0 );if (INTEL_GEN (dev_priv) <11 )
@@ -4043,6 +4042,34 @@ static u16 intel_get_ddb_size(struct drm_i915_private *dev_priv)return ddb_size; } +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry) +{ +u32 slice_mask =0 ; +u16 ddb_size =intel_get_ddb_size (dev_priv); +u16 num_supported_slices =INTEL_INFO (dev_priv)->num_supported_dbuf_slices; +u16 slice_size = ddb_size / num_supported_slices; +u16 start_slice; +u16 end_slice; + +if (!skl_ddb_entry_size (entry)) +return 0 ; + + start_slice = entry->start / slice_size; + end_slice = (entry->end -1 ) / slice_size; + +/* +* Per plane DDB entry can in a really worst case be on multiple slices +* but single entry is anyway contigious. +*/ +while (start_slice <= end_slice) { + slice_mask |=BIT (start_slice); + start_slice++; + } + +return slice_mask; +} +static u8 skl_compute_dbuf_slices (const struct intel_crtc_state *crtc_state,u8 active_pipes);
drivers/gpu/drm/i915/intel_pm.h +4 -0
@@ -39,6 +39,10 @@ u8 intel_enabled_dbuf_slices_mask(struct drm_i915_private *dev_priv);void skl_pipe_ddb_get_hw_state (struct intel_crtc *crtc,struct skl_ddb_entry *ddb_y,struct skl_ddb_entry *ddb_uv); +void skl_ddb_get_hw_state (struct drm_i915_private *dev_priv); +u16 intel_get_ddb_size (struct drm_i915_private *dev_priv); +u32 skl_ddb_dbuf_slice_mask (struct drm_i915_private *dev_priv, +const struct skl_ddb_entry *entry);void skl_pipe_wm_get_hw_state (struct intel_crtc *crtc,struct skl_pipe_wm *out);void g4x_wm_sanitize (struct drm_i915_private *dev_priv);
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
PATCH v9 7/7 drm/i915: Remove unneeded hack now for CDCLK
In reply to Stanislav LisovskiyNo need to bump up CDCLK now, as it is now correctly calculated, accounting for DBuf BW as BSpec says.
--- drivers/gpu/drm/i915/display/intel_cdclk.c | 12 ------------ 1 file changed, 12 deletions(-)
drivers/gpu/drm/i915/display/intel_cdclk.c +0 -12
@@ -2070,18 +2070,6 @@ int intel_crtc_compute_min_cdclk(const struct intel_crtc_state *crtc_state)/* Account for additional needs from the planes */ min_cdclk =max (intel_planes_min_cdclk (crtc_state), min_cdclk); -/* -* HACK. Currently for TGL platforms we calculate -* min_cdclk initially based on pixel_rate divided -* by 2, accounting for also plane requirements, -* however in some cases the lowest possible CDCLK -* doesn't work and causing the underruns. -* Explicitly stating here that this seems to be currently -* rather a Hack, than final solution. -*/ -if (IS_TIGERLAKE (dev_priv)) - min_cdclk =max (min_cdclk, (int )crtc_state->pixel_rate); -if (min_cdclk > dev_priv->max_cdclk_freq) { drm_dbg_kms(&dev_priv->drm, "required cdclk (%d kHz) exceeds max (%d kHz)\n",
Signature · 6 lines
2.24.1.485.gad05a3d8e5 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for Consider DBuf bandwidth when calculating CDCLK (rev14)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev14)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
Applying: drm/i915: Decouple cdclk calculation from modeset checks
Applying: drm/i915: Extract cdclk requirements checking to separate function
Applying: drm/i915: Check plane configuration properly
Applying: drm/i915: Plane configuration affects CDCLK in Gen11+
Applying: drm/i915: Introduce for_each_dbuf_slice_in_mask macro Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/display/intel_display_power.h
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/display/intel_display_power.h
Applying: drm/i915: Adjust CDCLK accordingly to our DBuf bw needs Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/display/intel_bw.c
M drivers/gpu/drm/i915/display/intel_bw.h
M drivers/gpu/drm/i915/display/intel_cdclk.c
M drivers/gpu/drm/i915/display/intel_display.c
M drivers/gpu/drm/i915/i915_drv.h
M drivers/gpu/drm/i915/intel_pm.c
M drivers/gpu/drm/i915/intel_pm.h
Falling back to patching base and 3-way merge...
Auto-merging drivers/gpu/drm/i915/intel_pm.h
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/intel_pm.h Auto-merging drivers/gpu/drm/i915/intel_pm.c
Auto-merging drivers/gpu/drm/i915/i915_drv.h
Auto-merging drivers/gpu/drm/i915/display/intel_display.c Auto-merging drivers/gpu/drm/i915/display/intel_cdclk.c Auto-merging drivers/gpu/drm/i915/display/intel_bw.h
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/display/intel_bw.h Auto-merging drivers/gpu/drm/i915/display/intel_bw.c
CONFLICT (content): Merge conflict in drivers/gpu/drm/i915/display/intel_bw.c
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch Patch failed at 0006 drm/i915: Adjust CDCLK accordingly to our DBuf bw needs When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Consider DBuf bandwidth when calculating CDCLK (rev15)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 42922a1cf4d9 drm/i915: Decouple cdclk calculation from modeset checks a2e2a5f43cd7 drm/i915: Extract cdclk requirements checking to separate function cc857a15d370 drm/i915: Check plane configuration properly -:32: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Stanislav Lisovskiy <[email protected]>'
total: 0 errors, 1 warnings, 0 checks, 14 lines checked4765b732c387 drm/i915: Plane configuration affects CDCLK in Gen11+
-:23: WARNING:NO_AUTHOR_SIGN_OFF: Missing Signed-off-by: line by nominal patch author 'Stanislav Lisovskiy <[email protected]>'
total: 0 errors, 1 warnings, 0 checks, 8 lines checked2405cfa20a90 drm/i915: Introduce for_each_dbuf_slice_in_mask macro -:25: CHECK:MACRO_ARG_REUSE: Macro argument reuse '__slice' - possible side-effects? #25: FILE: drivers/gpu/drm/i915/display/intel_display.h:190:
+#define for_each_dbuf_slice_in_mask(__slice, __mask) \
+ for ((__slice) = DBUF_S1; (__slice) < I915_MAX_DBUF_SLICES; (__slice)++) \
+ for_each_if((BIT(__slice)) & (__mask))
total: 0 errors, 0 warnings, 1 checks, 20 lines checked b74b713c823f drm/i915: Adjust CDCLK accordingly to our DBuf bw needs -:164: WARNING:LINE_SPACING: Missing a blank line after declarations #164: FILE: drivers/gpu/drm/i915/display/intel_bw.c:492:
+ int ret = intel_atomic_lock_global_state(&new_bw_state->base);
+ if (ret)
-:203: WARNING:LINE_SPACING: Missing a blank line after declarations #203: FILE: drivers/gpu/drm/i915/display/intel_bw.c:531:
+ int ret = intel_atomic_lock_global_state(&new_bw_state->base);
+ if (ret)
total: 0 errors, 2 warnings, 0 checks, 395 lines checked 2be3fecc6320 drm/i915: Remove unneeded hack now for CDCLK
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Consider DBuf bandwidth when calculating CDCLK (rev15)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.0 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/i915/display/intel_display.c:1222:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/display/intel_display.c:1225:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/display/intel_display.c:1228:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/display/intel_display.c:1231:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/gem/i915_gem_context.c:2274:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2275:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2276:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2277:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2278:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2279:17: error: bad integer constant expression +drivers/gpu/drm/i915/gt/intel_reset.c:1310:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block +drivers/gpu/drm/i915/gt/sysfs_engines.c:61:10: error: bad integer constant expression +drivers/gpu/drm/i915/gt/sysfs_engines.c:62:10: error: bad integer constant expression +drivers/gpu/drm/i915/gt/sysfs_engines.c:66:10: error: bad integer constant expression +drivers/gpu/drm/i915/gvt/mmio.c:287:23: warning: memcpy with byte count of 279040 +drivers/gpu/drm/i915/i915_perf.c:1425:15: warning: memset with byte count of 16777216 +drivers/gpu/drm/i915/i915_perf.c:1479:15: warning: memset with byte count of 16777216 +drivers/gpu/drm/i915/intel_wakeref.c:137:19: warning: context imbalance in 'wakeref_auto_timeout' - unexpected unlock +./include/linux/compiler.h:199:9: warning: context imbalance in 'engines_sample' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen8_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen8_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen8_write8' - different lock contexts for basic block
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8506 -> Patchwork_17718
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17718 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17718, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17718:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@client:
- fi-bsw-kefka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-bsw-kefka/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-bsw-kefka/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17718 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][3] -> [TIMEOUT][4] ([i915#1288])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-glk-dsi/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-glk-dsi/igt@[email protected]
* igt@i915_selftest@live@execlists:
- fi-kbl-guc: [PASS][5] -> [INCOMPLETE][6] ([i915#1874])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-guc/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-guc/igt@i915_selftest@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][7] -> [FAIL][8] ([i915#227])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-7500u/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-kbl-8809g: [INCOMPLETE][9] ([i915#1874]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-8809g/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-8809g/igt@i915_selftest@[email protected]
[i915#1288]: https://gitlab.freedesktop.org/drm/intel/issues/1288
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#227]: https://gitlab.freedesktop.org/drm/intel/issues/227
Participating hosts (49 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8506 -> Patchwork_17718
CI-20190529: 20190529
CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17718: 2be3fecc6320f61ccbd0898132dcb7eedae7640b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2be3fecc6320 drm/i915: Remove unneeded hack now for CDCLK b74b713c823f drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 2405cfa20a90 drm/i915: Introduce for_each_dbuf_slice_in_mask macro 4765b732c387 drm/i915: Plane configuration affects CDCLK in Gen11+ cc857a15d370 drm/i915: Check plane configuration properly a2e2a5f43cd7 drm/i915: Extract cdclk requirements checking to separate function 42922a1cf4d9 drm/i915: Decouple cdclk calculation from modeset checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
Self test failure as usual. And as usual not related to the patch.
Best Regards,
Lisovskiy Stanislav
________________________________________
From: Patchwork <[email protected]>
Sent: Wednesday, May 20, 2020 2:59 AM
To: Lisovskiy, Stanislav
Cc: [email protected]
Subject: ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8506 -> Patchwork_17718
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17718 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17718, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17718:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@client:
- fi-bsw-kefka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-bsw-kefka/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-bsw-kefka/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17718 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][3] -> [TIMEOUT][4] ([i915#1288])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-glk-dsi/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-glk-dsi/igt@[email protected]
* igt@i915_selftest@live@execlists:
- fi-kbl-guc: [PASS][5] -> [INCOMPLETE][6] ([i915#1874])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-guc/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-guc/igt@i915_selftest@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][7] -> [FAIL][8] ([i915#227])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-7500u/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-kbl-8809g: [INCOMPLETE][9] ([i915#1874]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-8809g/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-8809g/igt@i915_selftest@[email protected]
[i915#1288]: https://gitlab.freedesktop.org/drm/intel/issues/1288
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#227]: https://gitlab.freedesktop.org/drm/intel/issues/227
Participating hosts (49 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8506 -> Patchwork_17718
CI-20190529: 20190529
CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17718: 2be3fecc6320f61ccbd0898132dcb7eedae7640b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2be3fecc6320 drm/i915: Remove unneeded hack now for CDCLK b74b713c823f drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 2405cfa20a90 drm/i915: Introduce for_each_dbuf_slice_in_mask macro 4765b732c387 drm/i915: Plane configuration affects CDCLK in Gen11+ cc857a15d370 drm/i915: Check plane configuration properly a2e2a5f43cd7 drm/i915: Extract cdclk requirements checking to separate function 42922a1cf4d9 drm/i915: Decouple cdclk calculation from modeset checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
Filed a new bug and Re-reported.
-----Original Message-----
From: Lisovskiy, Stanislav <[email protected]>
Sent: Wednesday, May 20, 2020 9:22 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>; Saarinen, Jani <[email protected]>; Navare, Manasi D <[email protected]>
Subject: Re: ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
Self test failure as usual. And as usual not related to the patch.
Best Regards,
Lisovskiy Stanislav
________________________________________
From: Patchwork <[email protected]>
Sent: Wednesday, May 20, 2020 2:59 AM
To: Lisovskiy, Stanislav
Cc: [email protected]
Subject: ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8506 -> Patchwork_17718 ====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17718 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17718, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17718:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@client:
- fi-bsw-kefka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-bsw-kefka/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-bsw-kefka/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17718 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][3] -> [TIMEOUT][4] ([i915#1288])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-glk-dsi/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-glk-dsi/igt@[email protected]
* igt@i915_selftest@live@execlists:
- fi-kbl-guc: [PASS][5] -> [INCOMPLETE][6] ([i915#1874])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-guc/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-guc/igt@i915_selftest@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][7] -> [FAIL][8] ([i915#227])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-7500u/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-kbl-8809g: [INCOMPLETE][9] ([i915#1874]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-8809g/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-8809g/igt@i915_selftest@[email protected]
[i915#1288]: https://gitlab.freedesktop.org/drm/intel/issues/1288
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#227]: https://gitlab.freedesktop.org/drm/intel/issues/227
Participating hosts (49 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8506 -> Patchwork_17718
CI-20190529: 20190529
CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17718: 2be3fecc6320f61ccbd0898132dcb7eedae7640b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2be3fecc6320 drm/i915: Remove unneeded hack now for CDCLK b74b713c823f drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 2405cfa20a90 drm/i915: Introduce for_each_dbuf_slice_in_mask macro4765b732c387 drm/i915: Plane configuration affects CDCLK in Gen11+cc857a15d370 drm/i915: Check plane configuration properlya2e2a5f43cd7 drm/i915: Extract cdclk requirements checking to separate function42922a1cf4d9 drm/i915: Decouple cdclk calculation from modeset checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
Thank you Lakshmi!
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________________
From: Vudum, Lakshminarayana
Sent: Wednesday, May 20, 2020 11:43:26 AM
To: Lisovskiy, Stanislav; [email protected]; Saarinen, Jani; Navare, Manasi D
Subject: RE: ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
Filed a new bug and Re-reported.
-----Original Message-----
From: Lisovskiy, Stanislav <[email protected]>
Sent: Wednesday, May 20, 2020 9:22 AM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>; Saarinen, Jani <[email protected]>; Navare, Manasi D <[email protected]>
Subject: Re: ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
Self test failure as usual. And as usual not related to the patch.
Best Regards,
Lisovskiy Stanislav
________________________________________
From: Patchwork <[email protected]>
Sent: Wednesday, May 20, 2020 2:59 AM
To: Lisovskiy, Stanislav
Cc: [email protected]
Subject: ✗ Fi.CI.BAT: failure for Consider DBuf bandwidth when calculating CDCLK (rev15)
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8506 -> Patchwork_17718 ====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17718 absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17718, please notify your bug team to allow them to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17718:
### IGT changes ###
#### Possible regressions ####
* igt@i915_selftest@live@client:
- fi-bsw-kefka: [PASS][1] -> [INCOMPLETE][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-bsw-kefka/igt@i915_selftest@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-bsw-kefka/igt@i915_selftest@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17718 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][3] -> [TIMEOUT][4] ([i915#1288])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-glk-dsi/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-glk-dsi/igt@[email protected]
* igt@i915_selftest@live@execlists:
- fi-kbl-guc: [PASS][5] -> [INCOMPLETE][6] ([i915#1874])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-guc/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-guc/igt@i915_selftest@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][7] -> [FAIL][8] ([i915#227])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-7500u/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-kbl-8809g: [INCOMPLETE][9] ([i915#1874]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-8809g/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-8809g/igt@i915_selftest@[email protected]
[i915#1288]: https://gitlab.freedesktop.org/drm/intel/issues/1288
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#227]: https://gitlab.freedesktop.org/drm/intel/issues/227
Participating hosts (49 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8506 -> Patchwork_17718
CI-20190529: 20190529
CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17718: 2be3fecc6320f61ccbd0898132dcb7eedae7640b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2be3fecc6320 drm/i915: Remove unneeded hack now for CDCLK b74b713c823f drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 2405cfa20a90 drm/i915: Introduce for_each_dbuf_slice_in_mask macro4765b732c387 drm/i915: Plane configuration affects CDCLK in Gen11+cc857a15d370 drm/i915: Check plane configuration properlya2e2a5f43cd7 drm/i915: Extract cdclk requirements checking to separate function42922a1cf4d9 drm/i915: Decouple cdclk calculation from modeset checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Consider DBuf bandwidth when calculating CDCLK (rev15)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8506 -> Patchwork_17718
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
Known issues
------------
Here are the changes found in Patchwork_17718 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][1] -> [TIMEOUT][2] ([i915#1288])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-glk-dsi/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-glk-dsi/igt@[email protected]
* igt@i915_selftest@live@client:
- fi-bsw-kefka: [PASS][3] -> [INCOMPLETE][4] ([i915#1909])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-bsw-kefka/igt@i915_selftest@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-bsw-kefka/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@execlists:
- fi-kbl-guc: [PASS][5] -> [INCOMPLETE][6] ([i915#1874])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-guc/igt@i915_selftest@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-guc/igt@i915_selftest@[email protected]
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [PASS][7] -> [FAIL][8] ([i915#227])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-7500u/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-7500u/igt@[email protected]
#### Possible fixes ####
* igt@i915_selftest@live@execlists:
- fi-kbl-8809g: [INCOMPLETE][9] ([i915#1874]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/fi-kbl-8809g/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/fi-kbl-8809g/igt@i915_selftest@[email protected]
[i915#1288]: https://gitlab.freedesktop.org/drm/intel/issues/1288
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#1909]: https://gitlab.freedesktop.org/drm/intel/issues/1909
[i915#227]: https://gitlab.freedesktop.org/drm/intel/issues/227
Participating hosts (49 -> 44)
------------------------------
Additional (1): fi-kbl-7560u
Missing (6): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-byt-clapper fi-bdw-samus
Build changes
-------------
* Linux: CI_DRM_8506 -> Patchwork_17718
CI-20190529: 20190529
CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17718: 2be3fecc6320f61ccbd0898132dcb7eedae7640b @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
2be3fecc6320 drm/i915: Remove unneeded hack now for CDCLK b74b713c823f drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 2405cfa20a90 drm/i915: Introduce for_each_dbuf_slice_in_mask macro 4765b732c387 drm/i915: Plane configuration affects CDCLK in Gen11+ cc857a15d370 drm/i915: Check plane configuration properly a2e2a5f43cd7 drm/i915: Extract cdclk requirements checking to separate function 42922a1cf4d9 drm/i915: Decouple cdclk calculation from modeset checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Consider DBuf bandwidth when calculating CDCLK (rev18)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip 27d0a2a78122 drm/i915: Decouple cdclk calculation from modeset checks b0928a963b24 drm/i915: Extract cdclk requirements checking to separate function c013d7e44c52 drm/i915: Check plane configuration properly f6fbdfa19ab0 drm/i915: Plane configuration affects CDCLK in Gen11+ 89ece93a82af drm/i915: Introduce for_each_dbuf_slice_in_mask macro -:25: CHECK:MACRO_ARG_REUSE: Macro argument reuse '__slice' - possible side-effects? #25: FILE: drivers/gpu/drm/i915/display/intel_display.h:190: +#define for_each_dbuf_slice_in_mask(__slice, __mask) \ + for ((__slice) = DBUF_S1; (__slice) < I915_MAX_DBUF_SLICES; (__slice)++) \ + for_each_if((BIT(__slice)) & (__mask))
total: 0 errors, 0 warnings, 1 checks, 20 lines checked cea1d50d43c0 drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 727bc2568e96 drm/i915: Remove unneeded hack now for CDCLK
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.SPARSE: warning for Consider DBuf bandwidth when calculating CDCLK (rev18)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip Sparse version: v0.6.0 Fast mode used, each commit won't be checked separately. - +drivers/gpu/drm/i915/display/intel_display.c:1222:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/display/intel_display.c:1225:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/display/intel_display.c:1228:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/display/intel_display.c:1231:22: error: Expected constant expression in case statement +drivers/gpu/drm/i915/gem/i915_gem_context.c:2274:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2275:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2276:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2277:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2278:17: error: bad integer constant expression +drivers/gpu/drm/i915/gem/i915_gem_context.c:2279:17: error: bad integer constant expression +drivers/gpu/drm/i915/gt/intel_reset.c:1310:5: warning: context imbalance in 'intel_gt_reset_trylock' - different lock contexts for basic block +drivers/gpu/drm/i915/gt/sysfs_engines.c:61:10: error: bad integer constant expression +drivers/gpu/drm/i915/gt/sysfs_engines.c:62:10: error: bad integer constant expression +drivers/gpu/drm/i915/gt/sysfs_engines.c:66:10: error: bad integer constant expression +drivers/gpu/drm/i915/gvt/mmio.c:287:23: warning: memcpy with byte count of 279040 +drivers/gpu/drm/i915/i915_perf.c:1425:15: warning: memset with byte count of 16777216 +drivers/gpu/drm/i915/i915_perf.c:1479:15: warning: memset with byte count of 16777216 +drivers/gpu/drm/i915/intel_wakeref.c:137:19: warning: context imbalance in 'wakeref_auto_timeout' - unexpected unlock +./include/linux/compiler.h:199:9: warning: context imbalance in 'engines_sample' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen11_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen12_fwtable_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read64' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_read8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen6_write8' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen8_write16' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen8_write32' - different lock contexts for basic block +./include/linux/spinlock.h:408:9: warning: context imbalance in 'gen8_write8' - different lock contexts for basic block
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.BAT: success for Consider DBuf bandwidth when calculating CDCLK (rev18)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8511 -> Patchwork_17733
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/index.html
Known issues
------------
Here are the changes found in Patchwork_17733 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_pm_rpm@module-reload:
- fi-glk-dsi: [PASS][1] -> [TIMEOUT][2] ([i915#1288])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/fi-glk-dsi/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/fi-glk-dsi/igt@[email protected]
#### Possible fixes ####
* igt@i915_pm_rpm@module-reload:
- fi-kbl-guc: [SKIP][3] ([fdo#109271]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/fi-kbl-guc/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/fi-kbl-guc/igt@[email protected]
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[i915#1288]: https://gitlab.freedesktop.org/drm/intel/issues/1288
Participating hosts (48 -> 43)
------------------------------
Missing (5): fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-kbl-7560u fi-byt-clapper
Build changes
-------------
* Linux: CI_DRM_8511 -> Patchwork_17733
CI-20190529: 20190529
CI_DRM_8511: 504ee538bd65abff745914a6f0b7aad62bbc1d11 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5664: 404e2fa06b9c5986dec3fa210234fe8b034b157e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17733: 727bc2568e96653db48fa5821212abe6fb01b7a8 @ git://anongit.freedesktop.org/gfx-ci/linux
== Linux commits ==
727bc2568e96 drm/i915: Remove unneeded hack now for CDCLK cea1d50d43c0 drm/i915: Adjust CDCLK accordingly to our DBuf bw needs 89ece93a82af drm/i915: Introduce for_each_dbuf_slice_in_mask macro f6fbdfa19ab0 drm/i915: Plane configuration affects CDCLK in Gen11+ c013d7e44c52 drm/i915: Check plane configuration properly b0928a963b24 drm/i915: Extract cdclk requirements checking to separate function 27d0a2a78122 drm/i915: Decouple cdclk calculation from modeset checks
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for Consider DBuf bandwidth when calculating CDCLK (rev15)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev15)
URL : https://patchwork.freedesktop.org/series/74739/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8506_full -> Patchwork_17718_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Known issues
------------
Here are the changes found in Patchwork_17718_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_workarounds@suspend-resume-fd:
- shard-iclb: [PASS][1] -> [INCOMPLETE][2] ([i915#1185])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-iclb6/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-iclb3/igt@[email protected]
- shard-kbl: [PASS][3] -> [DMESG-WARN][4] ([i915#180]) +2 similar issues
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-kbl7/igt@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-kbl7/igt@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-skl: [PASS][5] -> [DMESG-WARN][6] ([i915#1436] / [i915#716]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl7/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl3/igt@[email protected]
* igt@i915_selftest@live@blt:
- shard-tglb: [PASS][7] -> [INCOMPLETE][8] ([i915#750])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-tglb7/igt@i915_selftest@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-tglb3/igt@i915_selftest@[email protected]
* igt@i915_selftest@live@execlists:
- shard-skl: [PASS][9] -> [INCOMPLETE][10] ([i915#1874])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl4/igt@i915_selftest@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl4/igt@i915_selftest@[email protected]
* igt@kms_cursor_crc@pipe-c-cursor-128x128-sliding:
- shard-glk: [PASS][11] -> [INCOMPLETE][12] ([i915#58] / [k.org#198133])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-glk8/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-glk9/igt@[email protected]
* igt@kms_hdr@bpc-switch-dpms:
- shard-skl: [PASS][13] -> [FAIL][14] ([i915#1188]) +1 similar issue
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl3/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl2/igt@[email protected]
* igt@kms_hdr@bpc-switch-suspend:
- shard-kbl: [PASS][15] -> [INCOMPLETE][16] ([i915#155])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-kbl2/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-kbl2/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-b-coverage-7efc:
- shard-skl: [PASS][17] -> [FAIL][18] ([fdo#108145] / [i915#265])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl5/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl10/igt@[email protected]
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][19] -> [SKIP][20] ([fdo#109441]) +2 similar issues
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-iclb1/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_setmode@basic:
- shard-skl: [PASS][21] -> [FAIL][22] ([i915#31])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl3/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl5/igt@[email protected]
* igt@kms_vblank@pipe-b-ts-continuation-suspend:
- shard-apl: [PASS][23] -> [DMESG-WARN][24] ([i915#180])
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-apl8/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-apl4/igt@[email protected]
#### Possible fixes ####
* igt@kms_cursor_crc@pipe-b-cursor-64x21-offscreen:
- shard-skl: [FAIL][25] ([i915#54]) -> [PASS][26] +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl4/igt@[email protected]
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl4/igt@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@b-edp1}:
- shard-skl: [INCOMPLETE][27] ([i915#198]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl5/igt@kms_flip@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl5/igt@kms_flip@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-kbl: [DMESG-WARN][29] ([i915#180]) -> [PASS][30] +3 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-kbl6/igt@kms_flip@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-kbl6/igt@kms_flip@[email protected]
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-cpu:
- shard-snb: [SKIP][31] ([fdo#109271]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-snb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-cpu.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-snb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-shrfb-draw-mmap-cpu.html
* igt@kms_hdr@bpc-switch-suspend:
- shard-skl: [FAIL][33] ([i915#1188]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl10/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl7/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][35] ([fdo#108145] / [i915#265]) -> [PASS][36] +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-skl2/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-skl7/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][37] ([fdo#109642] / [fdo#111068]) -> [PASS][38]
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-iclb8/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-iclb2/igt@[email protected]
* igt@kms_psr@psr2_sprite_mmap_gtt:
- shard-iclb: [SKIP][39] ([fdo#109441]) -> [PASS][40] +2 similar issues
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-iclb4/igt@kms_psr@psr2_sprite_mmap_gtt.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-iclb2/igt@kms_psr@psr2_sprite_mmap_gtt.html
* {igt@prime_vgem@sync@rcs0}:
- shard-iclb: [INCOMPLETE][41] ([i915#409]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-iclb8/igt@prime_vgem@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-iclb2/igt@prime_vgem@[email protected]
#### Warnings ####
* igt@kms_fbcon_fbt@fbc-suspend:
- shard-kbl: [DMESG-FAIL][43] ([i915#180] / [i915#95]) -> [FAIL][44] ([i915#1121] / [i915#93] / [i915#95])
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8506/shard-kbl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17718/shard-kbl2/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1121]: https://gitlab.freedesktop.org/drm/intel/issues/1121
[i915#1185]: https://gitlab.freedesktop.org/drm/intel/issues/1185
[i915#1188]: https://gitlab.freedesktop.org/drm/intel/issues/1188
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#198]: https://gitlab.freedesktop.org/drm/intel/issues/198
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#409]: https://gitlab.freedesktop.org/drm/intel/issues/409
[i915#54]: https://gitlab.freedesktop.org/drm/intel/issues/54
[i915#58]: https://gitlab.freedesktop.org/drm/intel/issues/58
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#750]: https://gitlab.freedesktop.org/drm/intel/issues/750
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#93]: https://gitlab.freedesktop.org/drm/intel/issues/93
[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
-------------
* Linux: CI_DRM_8506 -> Patchwork_17718
CI-20190529: 20190529
CI_DRM_8506: d6a73e9084ff6adfabbad014bc294d254484f304 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5661: a772a7c7a761c6125bc0af5284ad603478107737 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17718: 2be3fecc6320f61ccbd0898132dcb7eedae7640b @ 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_17718/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8511_full -> Patchwork_17733_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17733_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17733_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_17733_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-glk: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk1/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@kms_flip@plain-flip-fb-recreate-interruptible@c-hdmi-a2}:
- shard-glk: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk9/igt@kms_flip@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk7/igt@kms_flip@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17733_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile@bcs0:
- shard-iclb: [PASS][5] -> [FAIL][6] ([i915#1622])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-apl: [PASS][7] -> [DMESG-WARN][8] ([i915#180]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl7/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl4/igt@[email protected]
- shard-kbl: [PASS][9] -> [DMESG-WARN][10] ([i915#180]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][11] -> [INCOMPLETE][12] ([i915#155])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@i915_selftest@live@execlists:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([i915#1874])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl2/igt@i915_selftest@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl5/igt@i915_selftest@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-glk: [PASS][15] -> [FAIL][16] ([i915#1119] / [i915#118] / [i915#95])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement:
- shard-snb: [PASS][17] -> [SKIP][18] ([fdo#109271]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-snb4/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-snb1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render:
- shard-skl: [PASS][19] -> [FAIL][20] ([i915#49]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [PASS][21] -> [INCOMPLETE][22] ([i915#69])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][23] -> [FAIL][24] ([fdo#108145] / [i915#265]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb8/igt@kms_psr@psr2_no_drrs.html
#### Possible fixes ####
* igt@gem_ctx_persistence@engines-hostile@rcs0:
- shard-iclb: [FAIL][27] ([i915#1622]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed-process@blt:
- shard-skl: [FAIL][29] ([i915#1528]) -> [PASS][30] +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl3/igt@gem_ctx_persistence@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl1/igt@gem_ctx_persistence@[email protected]
* {igt@gem_exec_schedule@pi-distinct-iova@bcs0}:
- shard-glk: [FAIL][31] ([i915#859]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@gem_exec_schedule@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@gem_exec_schedule@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][33] ([i915#1436] / [i915#716]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl7/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][35] ([i915#454]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb6/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb5/igt@[email protected]
* igt@i915_suspend@fence-restore-untiled:
- shard-kbl: [DMESG-WARN][37] ([i915#180]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl3/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl4/igt@[email protected]
* {igt@kms_flip@flip-vs-expired-vblank@a-edp1}:
- shard-skl: [FAIL][39] ([i915#79]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@kms_flip@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl8/igt@kms_flip@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-apl: [DMESG-WARN][41] ([i915#180]) -> [PASS][42] +5 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl6/igt@kms_flip@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl2/igt@kms_flip@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][43] ([fdo#108145] / [i915#265]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl4/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [SKIP][45] ([fdo#109441]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][47] ([i915#31]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][49] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][50] ([i915#1319])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][51] ([fdo#110321]) -> [FAIL][52] ([fdo#110321])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl8/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl3/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][53] -> [SKIP][54] ([fdo#109642] / [fdo#111068])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb3/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1528]: https://gitlab.freedesktop.org/drm/intel/issues/1528
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1622]: https://gitlab.freedesktop.org/drm/intel/issues/1622
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#1883]: https://gitlab.freedesktop.org/drm/intel/issues/1883
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#859]: https://gitlab.freedesktop.org/drm/intel/issues/859
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8511 -> Patchwork_17733
CI-20190529: 20190529
CI_DRM_8511: 504ee538bd65abff745914a6f0b7aad62bbc1d11 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5664: 404e2fa06b9c5986dec3fa210234fe8b034b157e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17733: 727bc2568e96653db48fa5821212abe6fb01b7a8 @ 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_17733/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Seems to be unrelated issue. There seems to be some list corruption happening in drm fb manipulation code.
if those patches would be causing that (like some severe mem corruption)- it would happen much more broadly than single test and single platform. Moreover there is no direct connection to the changes.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________________
From: Patchwork <[email protected]>
Sent: Thursday, May 21, 2020 9:55:27 AM
To: Lisovskiy, Stanislav
Cc: [email protected]
Subject: ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8511_full -> Patchwork_17733_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17733_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17733_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_17733_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-glk: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk1/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@kms_flip@plain-flip-fb-recreate-interruptible@c-hdmi-a2}:
- shard-glk: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk9/igt@kms_flip@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk7/igt@kms_flip@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17733_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile@bcs0:
- shard-iclb: [PASS][5] -> [FAIL][6] ([i915#1622])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-apl: [PASS][7] -> [DMESG-WARN][8] ([i915#180]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl7/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl4/igt@[email protected]
- shard-kbl: [PASS][9] -> [DMESG-WARN][10] ([i915#180]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][11] -> [INCOMPLETE][12] ([i915#155])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@i915_selftest@live@execlists:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([i915#1874])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl2/igt@i915_selftest@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl5/igt@i915_selftest@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-glk: [PASS][15] -> [FAIL][16] ([i915#1119] / [i915#118] / [i915#95])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement:
- shard-snb: [PASS][17] -> [SKIP][18] ([fdo#109271]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-snb4/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-snb1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render:
- shard-skl: [PASS][19] -> [FAIL][20] ([i915#49]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [PASS][21] -> [INCOMPLETE][22] ([i915#69])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][23] -> [FAIL][24] ([fdo#108145] / [i915#265]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb8/igt@kms_psr@psr2_no_drrs.html
#### Possible fixes ####
* igt@gem_ctx_persistence@engines-hostile@rcs0:
- shard-iclb: [FAIL][27] ([i915#1622]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed-process@blt:
- shard-skl: [FAIL][29] ([i915#1528]) -> [PASS][30] +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl3/igt@gem_ctx_persistence@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl1/igt@gem_ctx_persistence@[email protected]
* {igt@gem_exec_schedule@pi-distinct-iova@bcs0}:
- shard-glk: [FAIL][31] ([i915#859]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@gem_exec_schedule@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@gem_exec_schedule@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][33] ([i915#1436] / [i915#716]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl7/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][35] ([i915#454]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb6/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb5/igt@[email protected]
* igt@i915_suspend@fence-restore-untiled:
- shard-kbl: [DMESG-WARN][37] ([i915#180]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl3/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl4/igt@[email protected]
* {igt@kms_flip@flip-vs-expired-vblank@a-edp1}:
- shard-skl: [FAIL][39] ([i915#79]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@kms_flip@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl8/igt@kms_flip@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-apl: [DMESG-WARN][41] ([i915#180]) -> [PASS][42] +5 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl6/igt@kms_flip@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl2/igt@kms_flip@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][43] ([fdo#108145] / [i915#265]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl4/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [SKIP][45] ([fdo#109441]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][47] ([i915#31]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][49] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][50] ([i915#1319])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][51] ([fdo#110321]) -> [FAIL][52] ([fdo#110321])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl8/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl3/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][53] -> [SKIP][54] ([fdo#109642] / [fdo#111068])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb3/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1528]: https://gitlab.freedesktop.org/drm/intel/issues/1528
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1622]: https://gitlab.freedesktop.org/drm/intel/issues/1622
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#1883]: https://gitlab.freedesktop.org/drm/intel/issues/1883
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#859]: https://gitlab.freedesktop.org/drm/intel/issues/859
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8511 -> Patchwork_17733
CI-20190529: 20190529
CI_DRM_8511: 504ee538bd65abff745914a6f0b7aad62bbc1d11 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5664: 404e2fa06b9c5986dec3fa210234fe8b034b157e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17733: 727bc2568e96653db48fa5821212abe6fb01b7a8 @ 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_17733/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Stan, I have addressed the issue and re-reported.
-----Original Message-----
From: Lisovskiy, Stanislav <[email protected]>
Sent: Thursday, May 21, 2020 12:36 PM
To: [email protected]; Vudum, Lakshminarayana <[email protected]>
Subject: Re: ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Seems to be unrelated issue. There seems to be some list corruption happening in drm fb manipulation code.
if those patches would be causing that (like some severe mem corruption)- it would happen much more broadly than single test and single platform. Moreover there is no direct connection to the changes.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________________
From: Patchwork <[email protected]>
Sent: Thursday, May 21, 2020 9:55:27 AM
To: Lisovskiy, Stanislav
Cc: [email protected]
Subject: ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_8511_full -> Patchwork_17733_full ====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_17733_full absolutely need to be verified manually.
If you think the reported changes have nothing to do with the changes introduced in Patchwork_17733_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_17733_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-glk: [PASS][1] -> [DMESG-FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk1/igt@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk1/igt@[email protected]
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@kms_flip@plain-flip-fb-recreate-interruptible@c-hdmi-a2}:
- shard-glk: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk9/igt@kms_flip@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk7/igt@kms_flip@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17733_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile@bcs0:
- shard-iclb: [PASS][5] -> [FAIL][6] ([i915#1622])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-apl: [PASS][7] -> [DMESG-WARN][8] ([i915#180]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl7/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl4/igt@[email protected]
- shard-kbl: [PASS][9] -> [DMESG-WARN][10] ([i915#180]) +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][11] -> [INCOMPLETE][12] ([i915#155])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@i915_selftest@live@execlists:
- shard-skl: [PASS][13] -> [INCOMPLETE][14] ([i915#1874])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl2/igt@i915_selftest@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl5/igt@i915_selftest@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-glk: [PASS][15] -> [FAIL][16] ([i915#1119] / [i915#118] / [i915#95])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement:
- shard-snb: [PASS][17] -> [SKIP][18] ([fdo#109271]) +1 similar issue
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-snb4/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-snb1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render:
- shard-skl: [PASS][19] -> [FAIL][20] ([i915#49]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [PASS][21] -> [INCOMPLETE][22] ([i915#69])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][23] -> [FAIL][24] ([fdo#108145] / [i915#265]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb8/igt@kms_psr@psr2_no_drrs.html
#### Possible fixes ####
* igt@gem_ctx_persistence@engines-hostile@rcs0:
- shard-iclb: [FAIL][27] ([i915#1622]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed-process@blt:
- shard-skl: [FAIL][29] ([i915#1528]) -> [PASS][30] +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl3/igt@gem_ctx_persistence@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl1/igt@gem_ctx_persistence@[email protected]
* {igt@gem_exec_schedule@pi-distinct-iova@bcs0}:
- shard-glk: [FAIL][31] ([i915#859]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@gem_exec_schedule@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@gem_exec_schedule@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][33] ([i915#1436] / [i915#716]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl7/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][35] ([i915#454]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb6/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb5/igt@[email protected]
* igt@i915_suspend@fence-restore-untiled:
- shard-kbl: [DMESG-WARN][37] ([i915#180]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl3/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl4/igt@[email protected]
* {igt@kms_flip@flip-vs-expired-vblank@a-edp1}:
- shard-skl: [FAIL][39] ([i915#79]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@kms_flip@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl8/igt@kms_flip@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-apl: [DMESG-WARN][41] ([i915#180]) -> [PASS][42] +5 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl6/igt@kms_flip@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl2/igt@kms_flip@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][43] ([fdo#108145] / [i915#265]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl4/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [SKIP][45] ([fdo#109441]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][47] ([i915#31]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][49] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][50] ([i915#1319])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][51] ([fdo#110321]) -> [FAIL][52] ([fdo#110321])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl8/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl3/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][53] -> [SKIP][54] ([fdo#109642] / [fdo#111068])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb3/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1528]: https://gitlab.freedesktop.org/drm/intel/issues/1528
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1622]: https://gitlab.freedesktop.org/drm/intel/issues/1622
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#1883]: https://gitlab.freedesktop.org/drm/intel/issues/1883
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#859]: https://gitlab.freedesktop.org/drm/intel/issues/859
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8511 -> Patchwork_17733
CI-20190529: 20190529
CI_DRM_8511: 504ee538bd65abff745914a6f0b7aad62bbc1d11 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5664: 404e2fa06b9c5986dec3fa210234fe8b034b157e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17733: 727bc2568e96653db48fa5821212abe6fb01b7a8 @ 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_17733/index.html
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
In reply to Lisovskiy, StanislavQuoting Lisovskiy, Stanislav (2020-05-21 10:35:42)
Quoted 2 lines
Seems to be unrelated issue. There seems to be some list corruption happening in drm fb manipulation code.
if those patches would be causing that (like some severe mem corruption)- it would happen much more broadly than single test and single platform. Moreover there is no direct connection to the changes.
The fi-glk-dsi failure in module reload is a result of this series. Somehow you have angered the i915 pm around snd_hda_intel.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/fi-glk-dsi/igt@[email protected]
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Quoting Chris Wilson (2020-05-22 23:00:10)
Quoted 7 lines
Quoting Lisovskiy, Stanislav (2020-05-21 10:35:42)
Quoted 2 lines
Seems to be unrelated issue. There seems to be some list corruption happening in drm fb manipulation code.
if those patches would be causing that (like some severe mem corruption)- it would happen much more broadly than single test and single platform. Moreover there is no direct connection to the changes.The fi-glk-dsi failure in module reload is a result of this series. Somehow you have angered the i915 pm around
snd_hda_intel.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/fi-glk-dsi/igt@[email protected]
CI says "drm/i915: Adjust CDCLK accordingly to our DBuf bw needs" is the culprit.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
I have seen those failures in other patches as well, i.e before my patches landed.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________________
From: Chris Wilson <[email protected]>
Sent: Saturday, May 23, 2020 2:18:44 AM
To: Lisovskiy, Stanislav; Vudum, Lakshminarayana; [email protected]
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Quoting Chris Wilson (2020-05-22 23:00:10)
Quoted 7 lines
Quoting Lisovskiy, Stanislav (2020-05-21 10:35:42)
Quoted 2 lines
Seems to be unrelated issue. There seems to be some list corruption happening in drm fb manipulation code.
if those patches would be causing that (like some severe mem corruption)- it would happen much more broadly than single test and single platform. Moreover there is no direct connection to the changes.The fi-glk-dsi failure in module reload is a result of this series. Somehow you have angered the i915 pm around
snd_hda_intel.
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/fi-glk-dsi/igt@[email protected]
CI says "drm/i915: Adjust CDCLK accordingly to our DBuf bw needs" is the culprit.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Quoting Lisovskiy, Stanislav (2020-05-25 09:00:33)
Quoted 1 line
I have seen those failures in other patches as well, i.e before my patches landed.
Look again. CI is very clear, as is the bisect and revert. -Chris
_______________________________________________
Intel-gfx mailing list [email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Ok, lets check - in worst case I just need to find a GLK machine and bisect.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________________
From: Chris Wilson <[email protected]>
Sent: Monday, May 25, 2020 11:03:36 AM
To: Lisovskiy, Stanislav; Vudum, Lakshminarayana; [email protected]
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Quoting Lisovskiy, Stanislav (2020-05-25 09:00:33)
Quoted 1 line
I have seen those failures in other patches as well, i.e before my patches landed.
Look again. CI is very clear, as is the bisect and revert. -Chris
_______________________________________________
Intel-gfx mailing list [email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Quoting Lisovskiy, Stanislav (2020-05-25 09:07:03)
Quoted 1 line
Ok, lets check - in worst case I just need to find a GLK machine and bisect.
Also there is https://gitlab.freedesktop.org/drm/intel/-/issues/1919 on icl.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
That one is different patch and moreover could be even won't fix. If we fail to disable qgv points - we fail. Could remove the message though if it floods the logs too much.
Best Regards,
Lisovskiy Stanislav
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
________________________________________
From: Chris Wilson <[email protected]>
Sent: Monday, May 25, 2020 11:09:37 AM
To: Lisovskiy, Stanislav; Vudum, Lakshminarayana; [email protected]
Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Consider DBuf bandwidth when calculating CDCLK (rev18)
Quoting Lisovskiy, Stanislav (2020-05-25 09:07:03)
Quoted 1 line
Ok, lets check - in worst case I just need to find a GLK machine and bisect.
Also there is https://gitlab.freedesktop.org/drm/intel/-/issues/1919 on icl.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Patchwork
CI[Intel-gfx] ✓ Fi.CI.IGT: success for Consider DBuf bandwidth when calculating CDCLK (rev18)
In reply to Stanislav Lisovskiy== Series Details ==
== Series Details ==
Series: Consider DBuf bandwidth when calculating CDCLK (rev18)
URL : https://patchwork.freedesktop.org/series/74739/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_8511_full -> Patchwork_17733_full
====================================================
Summary
-------
**SUCCESS**
No regressions found.
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_17733_full:
### IGT changes ###
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses. They do not affect the overall result.
* {igt@kms_flip@plain-flip-fb-recreate-interruptible@c-hdmi-a2}:
- shard-glk: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk9/igt@kms_flip@[email protected]
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk7/igt@kms_flip@[email protected]
Known issues
------------
Here are the changes found in Patchwork_17733_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_persistence@engines-hostile@bcs0:
- shard-iclb: [PASS][3] -> [FAIL][4] ([i915#1622])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_softpin@noreloc-s3:
- shard-apl: [PASS][5] -> [DMESG-WARN][6] ([i915#180]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl7/igt@[email protected]
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl4/igt@[email protected]
- shard-kbl: [PASS][7] -> [DMESG-WARN][8] ([i915#180]) +1 similar issue
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@gem_workarounds@suspend-resume-fd:
- shard-kbl: [PASS][9] -> [INCOMPLETE][10] ([i915#155])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl7/igt@[email protected]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl2/igt@[email protected]
* igt@i915_selftest@live@execlists:
- shard-skl: [PASS][11] -> [INCOMPLETE][12] ([i915#1874])
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl2/igt@i915_selftest@[email protected]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl5/igt@i915_selftest@[email protected]
* igt@kms_big_fb@x-tiled-64bpp-rotate-0:
- shard-glk: [PASS][13] -> [FAIL][14] ([i915#1119] / [i915#118] / [i915#95])
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@[email protected]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@[email protected]
* igt@kms_cursor_crc@pipe-a-cursor-128x128-rapid-movement:
- shard-snb: [PASS][15] -> [SKIP][16] ([fdo#109271]) +1 similar issue
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-snb4/igt@[email protected]
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-snb1/igt@[email protected]
* igt@kms_cursor_legacy@cursorb-vs-flipa-toggle:
- shard-glk: [PASS][17] -> [DMESG-FAIL][18] ([i915#1186])
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk1/igt@[email protected]
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk1/igt@[email protected]
* igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render:
- shard-skl: [PASS][19] -> [FAIL][20] ([i915#49]) +1 similar issue
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
- shard-skl: [PASS][21] -> [INCOMPLETE][22] ([i915#69])
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@[email protected]
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_plane_alpha_blend@pipe-a-coverage-7efc:
- shard-skl: [PASS][23] -> [FAIL][24] ([fdo#108145] / [i915#265]) +1 similar issue
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl9/igt@[email protected]
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl3/igt@[email protected]
* igt@kms_psr@psr2_no_drrs:
- shard-iclb: [PASS][25] -> [SKIP][26] ([fdo#109441]) +1 similar issue
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@kms_psr@psr2_no_drrs.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb8/igt@kms_psr@psr2_no_drrs.html
#### Possible fixes ####
* igt@gem_ctx_persistence@engines-hostile@rcs0:
- shard-iclb: [FAIL][27] ([i915#1622]) -> [PASS][28]
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@gem_ctx_persistence@[email protected]
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@gem_ctx_persistence@[email protected]
* igt@gem_ctx_persistence@legacy-engines-mixed-process@blt:
- shard-skl: [FAIL][29] ([i915#1528]) -> [PASS][30] +1 similar issue
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl3/igt@gem_ctx_persistence@[email protected]
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl1/igt@gem_ctx_persistence@[email protected]
* {igt@gem_exec_schedule@pi-distinct-iova@bcs0}:
- shard-glk: [FAIL][31] ([i915#859]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-glk6/igt@gem_exec_schedule@[email protected]
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-glk8/igt@gem_exec_schedule@[email protected]
* igt@gen9_exec_parse@allowed-all:
- shard-apl: [DMESG-WARN][33] ([i915#1436] / [i915#716]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl7/igt@[email protected]
* igt@i915_pm_dc@dc6-psr:
- shard-iclb: [FAIL][35] ([i915#454]) -> [PASS][36]
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb6/igt@[email protected]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb5/igt@[email protected]
* igt@i915_suspend@fence-restore-untiled:
- shard-kbl: [DMESG-WARN][37] ([i915#180]) -> [PASS][38] +1 similar issue
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-kbl3/igt@[email protected]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-kbl4/igt@[email protected]
* {igt@kms_flip@flip-vs-expired-vblank@a-edp1}:
- shard-skl: [FAIL][39] ([i915#79]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl4/igt@kms_flip@[email protected]
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl8/igt@kms_flip@[email protected]
* {igt@kms_flip@flip-vs-suspend-interruptible@c-dp1}:
- shard-apl: [DMESG-WARN][41] ([i915#180]) -> [PASS][42] +5 similar issues
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl6/igt@kms_flip@[email protected]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl2/igt@kms_flip@[email protected]
* igt@kms_plane_alpha_blend@pipe-c-coverage-7efc:
- shard-skl: [FAIL][43] ([fdo#108145] / [i915#265]) -> [PASS][44]
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-skl1/igt@[email protected]
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-skl4/igt@[email protected]
* igt@kms_psr@psr2_cursor_plane_move:
- shard-iclb: [SKIP][45] ([fdo#109441]) -> [PASS][46] +1 similar issue
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb3/igt@kms_psr@psr2_cursor_plane_move.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb2/igt@kms_psr@psr2_cursor_plane_move.html
* igt@kms_setmode@basic:
- shard-apl: [FAIL][47] ([i915#31]) -> [PASS][48]
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
#### Warnings ####
* igt@kms_content_protection@atomic:
- shard-apl: [FAIL][49] ([fdo#110321] / [fdo#110336]) -> [TIMEOUT][50] ([i915#1319])
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl2/igt@[email protected]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl1/igt@[email protected]
* igt@kms_content_protection@lic:
- shard-apl: [DMESG-FAIL][51] ([fdo#110321]) -> [FAIL][52] ([fdo#110321])
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-apl8/igt@[email protected]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-apl3/igt@[email protected]
* igt@kms_psr2_su@frontbuffer:
- shard-iclb: [SKIP][53] -> [SKIP][54] ([fdo#109642] / [fdo#111068])
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_8511/shard-iclb2/igt@[email protected]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_17733/shard-iclb3/igt@[email protected]
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#108145]: https://bugs.freedesktop.org/show_bug.cgi?id=108145
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#109642]: https://bugs.freedesktop.org/show_bug.cgi?id=109642
[fdo#110321]: https://bugs.freedesktop.org/show_bug.cgi?id=110321
[fdo#110336]: https://bugs.freedesktop.org/show_bug.cgi?id=110336
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[i915#1119]: https://gitlab.freedesktop.org/drm/intel/issues/1119
[i915#118]: https://gitlab.freedesktop.org/drm/intel/issues/118
[i915#1186]: https://gitlab.freedesktop.org/drm/intel/issues/1186
[i915#1319]: https://gitlab.freedesktop.org/drm/intel/issues/1319
[i915#1436]: https://gitlab.freedesktop.org/drm/intel/issues/1436
[i915#1528]: https://gitlab.freedesktop.org/drm/intel/issues/1528
[i915#1542]: https://gitlab.freedesktop.org/drm/intel/issues/1542
[i915#155]: https://gitlab.freedesktop.org/drm/intel/issues/155
[i915#1622]: https://gitlab.freedesktop.org/drm/intel/issues/1622
[i915#180]: https://gitlab.freedesktop.org/drm/intel/issues/180
[i915#1874]: https://gitlab.freedesktop.org/drm/intel/issues/1874
[i915#1883]: https://gitlab.freedesktop.org/drm/intel/issues/1883
[i915#265]: https://gitlab.freedesktop.org/drm/intel/issues/265
[i915#31]: https://gitlab.freedesktop.org/drm/intel/issues/31
[i915#454]: https://gitlab.freedesktop.org/drm/intel/issues/454
[i915#49]: https://gitlab.freedesktop.org/drm/intel/issues/49
[i915#69]: https://gitlab.freedesktop.org/drm/intel/issues/69
[i915#716]: https://gitlab.freedesktop.org/drm/intel/issues/716
[i915#79]: https://gitlab.freedesktop.org/drm/intel/issues/79
[i915#859]: https://gitlab.freedesktop.org/drm/intel/issues/859
[i915#95]: https://gitlab.freedesktop.org/drm/intel/issues/95
Participating hosts (11 -> 11)
------------------------------
No changes in participating hosts
Build changes
-------------
* Linux: CI_DRM_8511 -> Patchwork_17733
CI-20190529: 20190529
CI_DRM_8511: 504ee538bd65abff745914a6f0b7aad62bbc1d11 @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_5664: 404e2fa06b9c5986dec3fa210234fe8b034b157e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
Patchwork_17733: 727bc2568e96653db48fa5821212abe6fb01b7a8 @ 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_17733/index.html
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Pushed the series to dinq, thank you for patches and reviews
Regards
Manasi
Quoted 22 lines · Stanislav Lisovskiy
We need to calculate cdclk after watermarks/ddb has been calculated as with recent hw CDCLK needs to be adjusted accordingly to DBuf requirements, which is not possible with current code organization.
Setting CDCLK according to DBuf BW requirements and not just rejecting if it doesn't satisfy BW requirements, will allow us to save power when it is possible and gain additional bandwidth when it's needed - i.e boosting both our power management and perfomance capabilities.
This patch is preparation for that, first we now extract modeset calculation from modeset checks, in order to call it after wm/ddb has been calculated.
Stanislav Lisovskiy (7):
drm/i915: Decouple cdclk calculation from modeset checks drm/i915: Extract cdclk requirements checking to separate function drm/i915: Check plane configuration properly
drm/i915: Plane configuration affects CDCLK in Gen11+ drm/i915: Introducefor_each_dbuf_slice_in_maskmacro drm/i915: Adjust CDCLK accordingly to our DBuf bw needs drm/i915: Remove unneeded hack now for CDCLK
Quoted 15 lines
drivers/gpu/drm/i915/display/intel_bw.c | 118 +++++++++++++++++- drivers/gpu/drm/i915/display/intel_bw.h | 10 ++ drivers/gpu/drm/i915/display/intel_cdclk.c | 40 +++--- drivers/gpu/drm/i915/display/intel_cdclk.h | 1 - drivers/gpu/drm/i915/display/intel_display.c | 89 ++++++++++--- drivers/gpu/drm/i915/display/intel_display.h | 7 ++ .../drm/i915/display/intel_display_power.h | 1 + drivers/gpu/drm/i915/i915_drv.h | 1 + drivers/gpu/drm/i915/intel_pm.c | 31 ++++- drivers/gpu/drm/i915/intel_pm.h | 3 + 10 files changed, 261 insertions(+), 40 deletions(-)Signature · 1 line
2.24.1.485.gad05a3d8e5
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
Quoting Manasi Navare (2020-05-21 22:28:42)
Quoted 1 line
Pushed the series to dinq, thank you for patches and reviews
Could you tidy up the mess of the merge? Things like
cd19154608610ab4cdd6c039e9214b8dd281845c:
drivers/gpu/drm/i915/display/intel_bw.c +2 -1
@@ -6,11 +6,12 @@#include <drm/drm_atomic_state_helper.h> #include "intel_bw.h" +#include "intel_pm.h" #include "intel_display_types.h" #include "intel_sideband.h" #include "intel_atomic.h" #include "intel_pm.h" - +#include "intel_cdclk.h"
The out of place intel_atomic.h and intel_pm.h were added in 20f505f2253106f695ba6fa0a415159145a8fb2a
The code is a mess, checkpatch would be mad.
-Chris
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx