Re: [PATCH] x86, mtrr: mark range_new in mtrr_calc_range_state() as __initdata

* Rasmus Villemoes wrote: > On Fri, Nov 27 2015, Ingo Molnar wrote: > > > * Rasmus Villemoes wrote: > > > >> range_new doesn't seem to be used after init. It is only passed to > >> memset, sum_ranges, memcmp and x86_get_mtrr_mem_range, the latter of > >> which also only passes it on to variou

Re: [PATCH] x86, mtrr: mark range_new in mtrr_calc_range_state() as __initdata

On Fri, Nov 27 2015, Ingo Molnar wrote: > * Rasmus Villemoes wrote: > >> range_new doesn't seem to be used after init. It is only passed to >> memset, sum_ranges, memcmp and x86_get_mtrr_mem_range, the latter of >> which also only passes it on to various *range* library functions. So >> mark it

Re: [PATCH] x86, mtrr: mark range_new in mtrr_calc_range_state() as __initdata

* Rasmus Villemoes wrote: > range_new doesn't seem to be used after init. It is only passed to > memset, sum_ranges, memcmp and x86_get_mtrr_mem_range, the latter of > which also only passes it on to various *range* library functions. So > mark it __initdata to free up an extra page after init.