aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRasmus Villemoes <linux@rasmusvillemoes.dk>2015-12-01 15:44:50 -0500
committerIngo Molnar <mingo@kernel.org>2015-12-04 03:11:28 -0500
commitc332813b51cbe807d539bb059b81235abf1e3fdd (patch)
tree6cdca0850c8f281fe95bb30c54dc75620c9fed34
parent8609d1b5daa36350e020e737946c40887af1743a (diff)
x86/mm/mtrr: Mark the 'range_new' static variable in mtrr_calc_range_state() as __initdata
'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. Its contents are wiped at every call to mtrr_calc_range_state(), so it being static is not about preserving state between calls, but simply to avoid a 4k+ stack frame. While there, add a comment explaining this and why it's safe. We could also mark nr_range_new as __initdata, but since it's just a single int and also doesn't carry state between calls (it is unconditionally assigned to before it is read), we might as well make it an ordinary automatic variable. Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk> Cc: H. Peter Anvin <hpa@zytor.com> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Toshi Kani <toshi.kani@hp.com> Link: http://lkml.kernel.org/r/1449002691-20783-1-git-send-email-linux@rasmusvillemoes.dk Signed-off-by: Ingo Molnar <mingo@kernel.org>
-rw-r--r--arch/x86/kernel/cpu/mtrr/cleanup.c11
1 files changed, 9 insertions, 2 deletions
diff --git a/arch/x86/kernel/cpu/mtrr/cleanup.c b/arch/x86/kernel/cpu/mtrr/cleanup.c
index 70d7c93f4550..0d98503c2245 100644
--- a/arch/x86/kernel/cpu/mtrr/cleanup.c
+++ b/arch/x86/kernel/cpu/mtrr/cleanup.c
@@ -593,9 +593,16 @@ mtrr_calc_range_state(u64 chunk_size, u64 gran_size,
593 unsigned long x_remove_base, 593 unsigned long x_remove_base,
594 unsigned long x_remove_size, int i) 594 unsigned long x_remove_size, int i)
595{ 595{
596 static struct range range_new[RANGE_NUM]; 596 /*
597 * range_new should really be an automatic variable, but
598 * putting 4096 bytes on the stack is frowned upon, to put it
599 * mildly. It is safe to make it a static __initdata variable,
600 * since mtrr_calc_range_state is only called during init and
601 * there's no way it will call itself recursively.
602 */
603 static struct range range_new[RANGE_NUM] __initdata;
597 unsigned long range_sums_new; 604 unsigned long range_sums_new;
598 static int nr_range_new; 605 int nr_range_new;
599 int num_reg; 606 int num_reg;
600 607
601 /* Convert ranges to var ranges state: */ 608 /* Convert ranges to var ranges state: */