drm/i915: Allocate context objects from stolen
authorChris Wilson <chris@chris-wilson.co.uk>
Tue, 7 Apr 2015 15:21:11 +0000 (16:21 +0100)
committerDaniel Vetter <daniel.vetter@ffwll.ch>
Fri, 10 Apr 2015 08:41:24 +0000 (10:41 +0200)
commit149c86e74fe44dcbac5e9f8d145c5fbc5dc21261
treefe80ee5d681c97e8c91bbf7a712a2714e8d469d7
parentd7b9ca2f7a41cd36f5ca6c220df48ca9294ed37a
drm/i915: Allocate context objects from stolen

As we never expose context objects directly to userspace, we can forgo
allocating a first-class GEM object for them and prefer to use the
limited resource of reserved/stolen memory for them. Note this means
that their initial contents are undefined.

However, a downside of using stolen objects for execlists is that we
cannot access the physical address directly (thanks MCH!) which prevents
their use.

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