| Message ID | 20200519222342.6395-1-chris@chris-wilson.co.uk (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [CI] drm/i915/gt: Trace the CS interrupt | expand |
diff --git a/drivers/gpu/drm/i915/gt/intel_gt_irq.c b/drivers/gpu/drm/i915/gt/intel_gt_irq.c index 0cc7dd54f4f9..4291d55c5457 100644 --- a/drivers/gpu/drm/i915/gt/intel_gt_irq.c +++ b/drivers/gpu/drm/i915/gt/intel_gt_irq.c @@ -48,8 +48,12 @@ cs_irq_handler(struct intel_engine_cs *engine, u32 iir) tasklet = true; } - if (iir & GT_CONTEXT_SWITCH_INTERRUPT) + if (iir & GT_CONTEXT_SWITCH_INTERRUPT) { + ENGINE_TRACE(engine, "CS: %x %x\n", + ENGINE_READ_FW(engine, RING_EXECLIST_STATUS_HI), + ENGINE_READ_FW(engine, RING_EXECLIST_STATUS_LO)); tasklet = true; + } if (iir & GT_RENDER_USER_INTERRUPT) { intel_engine_signal_breadcrumbs(engine);
We have traces for the semaphore and the error, but not the far more frequent CS interrupts. This is likely to be too much, but for the purpose of live_unlite_preempt it may answer a question or two. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> --- drivers/gpu/drm/i915/gt/intel_gt_irq.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)