[Intel-gfx] [RFC PATCH 097/162] drm/i915: Distinction of memory regions
Chris Wilson
chris at chris-wilson.co.uk
Fri Nov 27 13:30:48 UTC 2020
Quoting Matthew Auld (2020-11-27 12:06:13)
> From: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
>
> IGTs should be able to choose testing strategy depending on memory
> regions and its sizes. Add region instance number to make this
> easier and descriptive.
>
> Cc: Matthew Auld <matthew.auld at intel.com>
> Cc: Ramalingam C <ramalingam.c at intel.com>
> Cc: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> Cc: Adam Miszczak <adam.miszczak at intel.com>
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski at intel.com>
> ---
> drivers/gpu/drm/i915/intel_memory_region.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_memory_region.c b/drivers/gpu/drm/i915/intel_memory_region.c
> index 1f26bc06ec20..cea44ddebe46 100644
> --- a/drivers/gpu/drm/i915/intel_memory_region.c
> +++ b/drivers/gpu/drm/i915/intel_memory_region.c
> @@ -329,6 +329,10 @@ int intel_memory_regions_hw_probe(struct drm_i915_private *i915)
> mem->instance = instance;
> mem->gt = &i915->gt;
>
> + if (HAS_LMEM(mem->i915) && type != INTEL_MEMORY_SYSTEM)
> + intel_memory_region_set_name(mem, "%s%u",
> + mem->name, mem->instance);
sprintf(mem->name, "%s", mem->name)
is that even defined behaviour?
-Chris
More information about the Intel-gfx
mailing list