drm/i915/gt: Introduce barrier pulses along engines

Browse source

To flush idle barriers, and even inflight requests, we want to send a
preemptive 'pulse' along an engine. We use a no-op request along the
pinned kernel_context at high priority so that it should run or else
kick off the stuck requests. We can use this to ensure idle barriers are
immediately flushed, as part of a context cancellation mechanism, or as
part of a heartbeat mechanism to detect and reset a stuck GPU.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20191021174339.5389-1-chris@chris-wilson.co.uk

...

This commit is contained in:

Chris Wilson 2019-10-21 18:43:39 +01:00

parent 928da10c0c

commit b5e8e954eb

8 changed files with 257 additions and 2 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

3

drivers/gpu/drm/i915/Makefile

View file

77

drivers/gpu/drm/i915/gt/intel_engine_heartbeat.c

View file

15

drivers/gpu/drm/i915/gt/intel_engine_heartbeat.h

View file

2

drivers/gpu/drm/i915/gt/intel_engine_pm.c

View file

159

drivers/gpu/drm/i915/gt/selftest_engine_heartbeat.c

View file

1

drivers/gpu/drm/i915/i915_active.c

View file

1

drivers/gpu/drm/i915/i915_priolist_types.h

View file

1

drivers/gpu/drm/i915/selftests/i915_live_selftests.h

View file