lkml.org 
[lkml]   [2013]   [May]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
Date
From
Subject[PATCH] 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>

---
arch/x86/include/asm/special_insns.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

--- 3.10-rc3/arch/x86/include/asm/special_insns.h
+++ 3.10-rc3-x86-force-order/arch/x86/include/asm/special_insns.h
@@ -16,7 +16,7 @@ static inline void native_clts(void)
* all loads stores around it, which can hurt performance. Solution is to
* use a variable and mimic reads and writes to it to enforce serialization
*/
-static unsigned long __force_order;
+extern unsigned long __force_order;

static inline unsigned long native_read_cr0(void)
{




\
 
 \ /
  Last update: 2013-05-29 15:01    [W:0.031 / U:0.080 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site