@@ -586,6 +586,8 @@ struct intel_fbc {
} work;
const char *no_fbc_reason;
+
+ bool cfb_try_resize;
};
/*
@@ -41,6 +41,9 @@
#include "intel_drv.h"
#include "i915_drv.h"
+static void __intel_fbc_cleanup_cfb(struct drm_i915_private *dev_priv);
+static int intel_fbc_alloc_cfb(struct intel_crtc *crtc);
+
static inline bool fbc_supported(struct drm_i915_private *dev_priv)
{
return HAS_FBC(dev_priv);
@@ -446,6 +449,15 @@ static void intel_fbc_work_fn(struct work_struct *__work)
goto retry;
}
+ if (fbc->cfb_try_resize) {
+ fbc->cfb_try_resize = false;
+ __intel_fbc_cleanup_cfb(dev_priv);
+ if (intel_fbc_alloc_cfb(crtc)) {
+ fbc->no_fbc_reason = "not enough stolen memory";
+ goto out;
+ }
+ }
+
intel_fbc_hw_activate(dev_priv);
work->scheduled = false;
@@ -846,22 +858,6 @@ static bool intel_fbc_can_activate(struct intel_crtc *crtc)
return false;
}
- /* It is possible for the required CFB size change without a
- * crtc->disable + crtc->enable since it is possible to change the
- * stride without triggering a full modeset. Since we try to
- * over-allocate the CFB, there's a chance we may keep FBC enabled even
- * if this happens, but if we exceed the current CFB size we'll have to
- * disable FBC. Notice that it would be possible to disable FBC, wait
- * for a frame, free the stolen node, then try to reenable FBC in case
- * we didn't get any invalidate/deactivate calls, but this would require
- * a lot of tracking just for a specific case. If we conclude it's an
- * important case, we can implement it later. */
- if (intel_fbc_calculate_cfb_size(dev_priv, &fbc->state_cache) >
- fbc->compressed_fb.size * fbc->threshold) {
- fbc->no_fbc_reason = "CFB requirements changed";
- return false;
- }
-
/*
* Work around a problem on GEN9+ HW, where enabling FBC on a plane
* having a Y offset that isn't divisible by 4 causes FIFO underrun
@@ -873,6 +869,22 @@ static bool intel_fbc_can_activate(struct intel_crtc *crtc)
return false;
}
+ if (!drm_mm_node_allocated(&fbc->compressed_fb))
+ return false;
+
+ /* It is possible for the required CFB size change without a
+ * crtc->disable + crtc->enable since it is possible to change the
+ * stride without triggering a full modeset. Since we try to
+ * over-allocate the CFB, there's a chance we may keep FBC enabled even
+ * if this happens, but if we exceed the current CFB size we'll have to
+ * resize CFB.
+ */
+ if (intel_fbc_calculate_cfb_size(dev_priv, &fbc->state_cache) >
+ (fbc->compressed_fb.size * fbc->threshold)) {
+ fbc->cfb_try_resize = true;
+ DRM_DEBUG_KMS("CFB memory requirements have changed");
+ }
+
return true;
}
@@ -1204,6 +1216,7 @@ void intel_fbc_enable(struct intel_crtc *crtc,
fbc->enabled = true;
fbc->crtc = crtc;
+ fbc->cfb_try_resize = false;
out:
mutex_unlock(&fbc->lock);
}
A simple page flip can cause the CFB required size to increase and if it is bigger than the currently allocated CFB it needs to be resized to activate FBC again. Until now this case was not being handled but CI is starting to get some of this errors. So here it will free the old CFB and try to allocate the required CFB in the schedule activation work, it will happen after one vblank so is guarantee that FBC was completed disabled and is not using CFB. Cc: Paulo Zanoni <paulo.r.zanoni@intel.com> Signed-off-by: José Roberto de Souza <jose.souza@intel.com> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=105683 --- drivers/gpu/drm/i915/i915_drv.h | 2 ++ drivers/gpu/drm/i915/intel_fbc.c | 45 ++++++++++++++++++++------------ 2 files changed, 31 insertions(+), 16 deletions(-)