drm/i915: Mark the end of intel_ring_begin() and check in intel_ring_advance()
authorChris Wilson <chris@chris-wilson.co.uk>
Mon, 6 Feb 2017 17:05:01 +0000 (17:05 +0000)
committerChris Wilson <chris@chris-wilson.co.uk>
Mon, 6 Feb 2017 20:41:00 +0000 (20:41 +0000)
commiteca56a35111c9e6663fbcd7dc37bcc572367efa3
treecff32da1966812f4d4e91ddf31d7e7deb872f372
parent04da811b3d821567e7a9a8a0baf48a6c1718b582
drm/i915: Mark the end of intel_ring_begin() and check in intel_ring_advance()

It is required that the caller declare the exact number of dwords they
wish to write into the ring. This is required for two reasons, we need
to allocate sufficient space for the entire command packet and we need
to be sure that the contents are completely written to avoid executing
stale data. The current interface requires for any bug to be caught in
review, the reader has to carefully count the number of
intel_ring_emit() between intel_ring_begin() and intel_ring_advance().
If we record the end of the packet of each intel_ring_begin() we can
also have CI check for us.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20170206170502.30944-1-chris@chris-wilson.co.uk
drivers/gpu/drm/i915/i915_gem.h
drivers/gpu/drm/i915/intel_ringbuffer.c
drivers/gpu/drm/i915/intel_ringbuffer.h