[PATCH 4/6] drm/i915/guc: Call invalidate after changing the vfunc

Michał Winiarski michal.winiarski at intel.com
Tue Dec 12 21:10:37 UTC 2017

To make this operation a bit cleaner, we should make sure that the HW
can catch up by calling the new implementation right away.
Note that currently we're only touching the vfunc at module load time
(before GuC is even loaded), so this shouldn't cause any functional

Suggested-by: Chris Wilson <chris at chris-wilson.co.uk>
Signed-off-by: Michał Winiarski <michal.winiarski at intel.com>
Cc: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
 drivers/gpu/drm/i915/i915_gem_gtt.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/gpu/drm/i915/i915_gem_gtt.c b/drivers/gpu/drm/i915/i915_gem_gtt.c
index a7fe05666f72..5fd9c4f05928 100644
--- a/drivers/gpu/drm/i915/i915_gem_gtt.c
+++ b/drivers/gpu/drm/i915/i915_gem_gtt.c
@@ -3553,6 +3553,8 @@ void i915_ggtt_enable_guc(struct drm_i915_private *i915)
 	GEM_BUG_ON(i915->ggtt.invalidate != gen6_ggtt_invalidate);
 	i915->ggtt.invalidate = guc_ggtt_invalidate;
+	i915_ggtt_invalidate(i915);
 void i915_ggtt_disable_guc(struct drm_i915_private *i915)
@@ -3561,6 +3563,8 @@ void i915_ggtt_disable_guc(struct drm_i915_private *i915)
 	GEM_BUG_ON(i915->ggtt.invalidate != guc_ggtt_invalidate);
 	i915->ggtt.invalidate = gen6_ggtt_invalidate;
+	i915_ggtt_invalidate(i915);
 void i915_gem_restore_gtt_mappings(struct drm_i915_private *dev_priv)

More information about the Intel-gfx-trybot mailing list