Chris Wilson <[email protected]> writes: > Since a global reset affects the engine, include that along side the > per-engine reset counter when pretty printing the engine state in > intel_engine_dump(). > > Signed-off-by: Chris Wilson <[email protected]> > Cc: Mika Kuoppala <[email protected]>
Reviewed-by: Mika Kuoppala <[email protected]> > --- > drivers/gpu/drm/i915/intel_engine_cs.c | 5 +++-- > 1 file changed, 3 insertions(+), 2 deletions(-) > > diff --git a/drivers/gpu/drm/i915/intel_engine_cs.c > b/drivers/gpu/drm/i915/intel_engine_cs.c > index aa490120749a..2ab18eb10d52 100644 > --- a/drivers/gpu/drm/i915/intel_engine_cs.c > +++ b/drivers/gpu/drm/i915/intel_engine_cs.c > @@ -1679,8 +1679,9 @@ void intel_engine_dump(struct intel_engine_cs *engine, > engine->hangcheck.seqno, > jiffies_to_msecs(jiffies - > engine->hangcheck.action_timestamp), > engine->timeline->inflight_seqnos); > - drm_printf(m, "\tReset count: %d\n", > - i915_reset_engine_count(error, engine)); > + drm_printf(m, "\tReset count: %d (global %d)\n", > + i915_reset_engine_count(error, engine), > + i915_reset_count(error)); > > rcu_read_lock(); > > -- > 2.15.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
