drm/i915: only one interrupt per batchbuffer is not enough!
authorDaniel Vetter <daniel.vetter@ffwll.ch>
Tue, 2 Feb 2010 16:08:37 +0000 (17:08 +0100)
committerChris Wilson <chris@chris-wilson.co.uk>
Wed, 8 Sep 2010 09:23:35 +0000 (10:23 +0100)
commita6910434e1b5f2a9fe7cab39b01bae9a7a7bbe70
treecc4778226ba2cb98e6daf1d6ba86f1a7273aa04f
parent8bff917c93e365a8a145f9b1be99c81257038151
drm/i915: only one interrupt per batchbuffer is not enough!

Previously I thought that one interrupt per batchbuffer should be
enough. Now tedious benchmarking showed this to be wrong.

Therefore track whether any commands have been isssued with a future
seqno (like pipelined fencing changes or flushes). If this is the case
emit a request before issueing the batchbuffer.

Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
drivers/gpu/drm/i915/i915_drv.h
drivers/gpu/drm/i915/i915_gem.c
drivers/gpu/drm/i915/intel_ringbuffer.h