drm/i915: Allow ringbuffers to be bound anywhere

Now that we have WC vmapping available, we can bind our rings anywhere
in the GGTT and do not need to restrict them to the mappable region.
Except for stolen objects, for which direct access is verbatim and we
must use the mappable aperture.

Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20160818161718.27187-17-chris@chris-wilson.co.uk
This commit is contained in:
Chris Wilson
2016-08-18 17:16:56 +01:00
parent 05a20d098d
commit 9d80841ea4
2 changed files with 8 additions and 8 deletions

View File

@@ -96,7 +96,6 @@ struct intel_ring {
int space;
int size;
int effective_size;
bool needs_iomap;
/** We track the position of the requests in the ring buffer, and
* when each is retired we increment last_retired_head as the GPU