Quoting Matthew Auld (2017-11-24 21:29:28) Always have a small explanation here. "Now that we are using struct resource to track the stolen region, it is more convenient if we track the reserved portion of that region in a resource as well." > v2: s/<= end + 1/< end/ (Chris) > > Signed-off-by: Matthew Auld <matthew.auld@xxxxxxxxx> > Cc: Joonas Lahtinen <joonas.lahtinen@xxxxxxxxxxxxxxx> > Cc: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx> > Cc: Paulo Zanoni <paulo.r.zanoni@xxxxxxxxx> > --- > @@ -400,17 +401,16 @@ int i915_gem_init_stolen(struct drm_i915_private *dev_priv) > reserved_base = stolen_top; > } > > - if (reserved_base < dev_priv->dsm.start || > - reserved_base + reserved_size > stolen_top) { > - dma_addr_t reserved_top = reserved_base + reserved_size; > - DRM_ERROR("Stolen reserved area [%pad - %pad] outside stolen memory [%pad - %pad]\n", > - &reserved_base, &reserved_top, > - &dev_priv->dsm.start, &stolen_top); > + reserved.start = reserved_base; > + reserved.end = reserved_base + reserved_size - 1; Not just dev_priv->dsm_reserved = DEFINE_RES_MEM(reserved_base, reserved_size); ? -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx