Quoting Matthew Auld (2017-12-11 12:14:20) > From: Joonas Lahtinen <[email protected]> > > To give upcoming SKU BIOSes more flexibility in placing the Intel > graphics stolen memory, make all variables storing the placement or size > compatible with full 64 bit range. Also by exporting the stolen region > as a resource, we can then nuke the duplicated stolen discovery in i915. > > Signed-off-by: Joonas Lahtinen <[email protected]> > Signed-off-by: Matthew Auld <[email protected]> > Cc: Joonas Lahtinen <[email protected]> > Cc: Ville Syrjälä <[email protected]> > Cc: Chris Wilson <[email protected]> > Cc: Paulo Zanoni <[email protected]> > Cc: Thomas Gleixner <[email protected]> > Cc: Ingo Molnar <[email protected]> > Cc: H. Peter Anvin <[email protected]> > Cc: [email protected] > Cc: [email protected] > Reviewed-by: Chris Wilson <[email protected]> #v3 > --- > diff --git a/include/drm/i915_drm.h b/include/drm/i915_drm.h > index 4e1b274e1164..c9e5a6621b95 100644 > --- a/include/drm/i915_drm.h > +++ b/include/drm/i915_drm.h > @@ -36,6 +36,9 @@ extern bool i915_gpu_lower(void); > extern bool i915_gpu_busy(void); > extern bool i915_gpu_turbo_disable(void); > > +/* Exported from arch/x86/kernel/early-quirks.c */ > +extern struct resource intel_graphics_stolen_res;
It would be nice if we could flag to the compiler that it was always const when exported. But I don't think that's possible with C's type annotations. Reviewed-by: Chris Wilson <[email protected]> -Chris _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
