summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorMatthew Auld <matthew.auld@intel.com>2019-10-08 17:01:14 +0100
committerChris Wilson <chris@chris-wilson.co.uk>2019-10-08 20:49:55 +0100
commit232a6ebae419193f5b8da4fa869ae5089ab105c2 (patch)
treed27f4ef38adf7279ea044f070a632e7c6284ab97 /include/linux
parentd99f7b079c2a49b2278fe80192fbca083db87d18 (diff)
downloadcachepc-linux-232a6ebae419193f5b8da4fa869ae5089ab105c2.tar.gz
cachepc-linux-232a6ebae419193f5b8da4fa869ae5089ab105c2.zip
drm/i915: introduce intel_memory_region
Support memory regions, as defined by a given (start, end), and allow creating GEM objects which are backed by said region. The immediate goal here is to have something to represent our device memory, but later on we also want to represent every memory domain with a region, so stolen, shmem, and of course device. At some point we are probably going to want use a common struct here, such that we are better aligned with say TTM. Signed-off-by: Matthew Auld <matthew.auld@intel.com> Signed-off-by: Abdiel Janulgue <abdiel.janulgue@linux.intel.com> Signed-off-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Link: https://patchwork.freedesktop.org/patch/msgid/20191008160116.18379-2-matthew.auld@intel.com
Diffstat (limited to 'include/linux')
0 files changed, 0 insertions, 0 deletions