Quoting Matthew Auld (2017-12-05 21:02:48)
> @@ -381,8 +381,8 @@ struct i915_ggtt {
> * avoid the first page! The upper end of stolen memory is reserved
> for
> * hardware functions and similarly removed from the accessible range.
> */
> - u32 stolen_size; /* Total size of stolen memory */
> - u32 stolen_usable_size; /* Total size minus reserved ranges */
> + resource_size_t stolen_size; /* Total size of stolen
> memory */
> + resource_size_t stolen_usable_size; /* Total size minus reserved
> ranges */
Why does stolen_size still exist now that we have stuct resource dsm?
Worst case it is resource_size(&dsm), but in most cases you actually
want to know dsm.end afaict.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
