Quoting Matthew Auld (2017-12-06 18:17:28)
> Kick it out of i915_ggtt and keep it grouped with dsm and dsm_reserved,
> where it makes the most sense.
>
> Signed-off-by: Matthew Auld <matthew.a...@intel.com>
> Cc: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
> Cc: Chris Wilson <ch...@chris-wilson.co.uk>
> Cc: Paulo Zanoni <paulo.r.zan...@intel.com>
> ---
> drivers/gpu/drm/i915/i915_drv.h | 12 +++++++++++-
> drivers/gpu/drm/i915/i915_gem_gtt.h | 10 ----------
> drivers/gpu/drm/i915/i915_gem_stolen.c | 5 ++---
> drivers/gpu/drm/i915/intel_display.c | 3 +--
> drivers/gpu/drm/i915/intel_fbdev.c | 3 +--
> 5 files changed, 15 insertions(+), 18 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index 40171a7da9d9..2c3e1d715c11 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -2253,7 +2253,7 @@ struct drm_i915_private {
> /**
> * Data Stolen Memory - aka "i915 stolen memory" gives us the start
> and
> * end of stolen which we can optionally use to create GEM objects
> - * backed by stolen memory. Note that ggtt->stolen_usable_size tells
> us
> + * backed by stolen memory. Note that stolen_usable_size tells us
> * exactly how much of this we are actually allowed to use, given that
> * some portion of it is in fact reserved for use by hardware
> functions.
> */
> @@ -2263,6 +2263,16 @@ struct drm_i915_private {
> */
> struct resource dsm_reserved;
>
> + /* Stolen memory is segmented in hardware with different portions
/*
* Stolen...
*/
Reviewed-by: Chris Wilson <ch...@chris-wilson.co.uk>
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
