forked from Minki/linux
4a234c5fae
The vma already contains most of the information we need for insertion. But also in preparation for supporting huge gtt pages, it would be useful to know the details of the vma, such that we can we can easily determine the page sizes we are allowed to use when inserting into the 48b PPGTT. This is especially true for 64K where we can't just arbitrarily use it, since we require aligning/padding the vm space to 2M, which sometimes we can't enforce in the upper levels. Suggested-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Matthew Auld <matthew.auld@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Link: http://patchwork.freedesktop.org/patch/msgid/20170622095836.6800-1-matthew.auld@intel.com Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> |
||
|---|---|---|
| .. | ||
| huge_gem_object.c | ||
| huge_gem_object.h | ||
| i915_gem_coherency.c | ||
| i915_gem_context.c | ||
| i915_gem_dmabuf.c | ||
| i915_gem_evict.c | ||
| i915_gem_gtt.c | ||
| i915_gem_object.c | ||
| i915_gem_request.c | ||
| i915_gem_timeline.c | ||
| i915_live_selftests.h | ||
| i915_mock_selftests.h | ||
| i915_random.c | ||
| i915_random.h | ||
| i915_selftest.c | ||
| i915_sw_fence.c | ||
| i915_syncmap.c | ||
| i915_vma.c | ||
| intel_breadcrumbs.c | ||
| intel_hangcheck.c | ||
| intel_uncore.c | ||
| mock_context.c | ||
| mock_context.h | ||
| mock_dmabuf.c | ||
| mock_dmabuf.h | ||
| mock_drm.c | ||
| mock_drm.h | ||
| mock_engine.c | ||
| mock_engine.h | ||
| mock_gem_device.c | ||
| mock_gem_device.h | ||
| mock_gem_object.h | ||
| mock_gtt.c | ||
| mock_gtt.h | ||
| mock_request.c | ||
| mock_request.h | ||
| mock_timeline.c | ||
| mock_timeline.h | ||
| mock_uncore.c | ||
| mock_uncore.h | ||
| scatterlist.c | ||