summaryrefslogtreecommitdiff
path: root/drivers/gpu/drm/i915/intel_memory_region.h
diff options
context:
space:
mode:
authorTvrtko Ursulin <tvrtko.ursulin@intel.com>2023-11-07 10:18:05 +0000
committerTvrtko Ursulin <tvrtko.ursulin@intel.com>2023-11-10 11:49:06 +0000
commit3b38d35157530c12c84fc02cccd469b9a0a00ae7 (patch)
treef9805157cbd86606a8a5c4ba4a45c5df0a43fd6a /drivers/gpu/drm/i915/intel_memory_region.h
parentdc1a2775070f0618b661500310b2ea8643592ed1 (diff)
downloadlinux-3b38d35157530c12c84fc02cccd469b9a0a00ae7.tar.gz
linux-3b38d35157530c12c84fc02cccd469b9a0a00ae7.tar.bz2
linux-3b38d35157530c12c84fc02cccd469b9a0a00ae7.zip
drm/i915: Add stable memory region names
At the moment memory region names are a bit too varied and too inconsistent to be used for ABI purposes, like for upcoming fdinfo memory stats. System memory can be either system or system-ttm. Local memory has the instance number appended, others do not. Not only incosistent but thi kind of implementation detail is uninteresting for intended users of fdinfo memory stats. Add a stable name always formed as $type$instance. Could have chosen a different stable scheme, but I think any consistent and stable scheme should do just fine. Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Aravind Iddamsetty <aravind.iddamsetty@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20231107101806.608990-5-tvrtko.ursulin@linux.intel.com
Diffstat (limited to 'drivers/gpu/drm/i915/intel_memory_region.h')
-rw-r--r--drivers/gpu/drm/i915/intel_memory_region.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/intel_memory_region.h b/drivers/gpu/drm/i915/intel_memory_region.h
index 2953ed5c3248..9ba36454e51b 100644
--- a/drivers/gpu/drm/i915/intel_memory_region.h
+++ b/drivers/gpu/drm/i915/intel_memory_region.h
@@ -80,6 +80,7 @@ struct intel_memory_region {
u16 instance;
enum intel_region_id id;
char name[16];
+ char uabi_name[16];
bool private; /* not for userspace */
struct {