[RFC v5 4/8] drm/i915: Park before resetting the submission backend
Michal Wajdeczko
michal.wajdeczko at intel.com
Mon Jan 14 13:18:48 UTC 2019
From: Chris Wilson <chris at chris-wilson.co.uk>
As different backends may have different park/unpark callbacks, we
should only ever switch backends (reset_default_submission on wedge
recovery, or on enabling the guc) while parked.
v2: Remove the assert from the guc code, as we are currently trying to
modify the engine vfuncs pointer on a live system after reset (not just
wedging). We will just have to hope that the system is balanced.
v3: Rebase onto __i915_gem_park and improve grammar.
Signed-off-by: Chris Wilson <chris at chris-wilson.co.uk>
Cc: Michal Wajdeczko <michal.wajdeczko at intel.com>
Cc: Sagar Arun Kamble <sagar.a.kamble at intel.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
Cc: Mika Kuoppala <mika.kuoppala at linux.intel.com>
Reviewed-by: Sagar Arun Kamble <sagar.a.kamble at intel.com>
Reviewed-by: Michal Wajdeczko <michal.wajdeczko at intel.com>
---
drivers/gpu/drm/i915/i915_gem.c | 15 ++++++++++++---
drivers/gpu/drm/i915/intel_engine_cs.c | 3 +++
2 files changed, 15 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c
index ea85da393662..a4435a807e83 100644
--- a/drivers/gpu/drm/i915/i915_gem.c
+++ b/drivers/gpu/drm/i915/i915_gem.c
@@ -147,8 +147,6 @@ static u32 __i915_gem_park(struct drm_i915_private *i915)
if (!i915->gt.awake)
return I915_EPOCH_INVALID;
- GEM_BUG_ON(i915->gt.epoch == I915_EPOCH_INVALID);
-
/*
* Be paranoid and flush a concurrent interrupt to make sure
* we don't reactivate any irq tasklets after parking.
@@ -177,6 +175,7 @@ static u32 __i915_gem_park(struct drm_i915_private *i915)
intel_runtime_pm_put(i915);
+ GEM_BUG_ON(i915->gt.epoch == I915_EPOCH_INVALID);
return i915->gt.epoch;
}
@@ -3268,7 +3267,17 @@ bool i915_gem_unset_wedged(struct drm_i915_private *i915)
return false;
}
i915_retire_requests(i915);
- GEM_BUG_ON(i915->gt.active_requests);
+
+ /*
+ * Park before disengaging the old submit mechanism as different
+ * backends may have different park/unpack callbacks.
+ *
+ * We are idle; the idle-worker will be queued, but we need to run
+ * it now. As we already hold the struct mutex, we can park the GPU
+ * right away, letting the lazy worker see that we are already active
+ * again by the time it acquires the mutex.
+ */
+ __i915_gem_park(i915);
intel_engines_sanitize(i915, false);
diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c b/drivers/gpu/drm/i915/intel_engine_cs.c
index 236cd040f271..1ee37e8cee0f 100644
--- a/drivers/gpu/drm/i915/intel_engine_cs.c
+++ b/drivers/gpu/drm/i915/intel_engine_cs.c
@@ -1039,6 +1039,9 @@ void intel_engines_reset_default_submission(struct drm_i915_private *i915)
struct intel_engine_cs *engine;
enum intel_engine_id id;
+ /* Must be parked first! */
+ GEM_BUG_ON(i915->gt.awake);
+
for_each_engine(engine, i915, id)
engine->set_default_submission(engine);
}
--
2.19.2
More information about the Intel-gfx-trybot
mailing list