x86: __force_order doesn't need to be an actual variable
authorJan Beulich <JBeulich@suse.com>
Wed, 29 May 2013 12:29:12 +0000 (13:29 +0100)
committerIngo Molnar <mingo@kernel.org>
Fri, 31 May 2013 11:09:17 +0000 (13:09 +0200)
commit1d10f6ee602ec5a4bd0c1606ba5f38277da432e1
tree78400a0f9b9d13313982e3f6537195e9401b8a0c
parentdcdbe33add56cb659ebf21fb9b6577507e21d952
x86: __force_order doesn't need to be an actual variable

It being static causes over a dozen instances to be scattered
across the kernel image, with non of them ever being referenced
in any way. Making the variable extern without ever defining it
works as well - all we need is to have the compiler think the
variable is being accessed.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Link: http://lkml.kernel.org/r/51A610B802000078000D99A0@nat28.tlf.novell.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
arch/x86/include/asm/special_insns.h