lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20070729150248.GA16817@stusta.de>
Date:	Sun, 29 Jul 2007 17:02:48 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: [2.6 patch] i386: no need to make enable_cpu_hotplug a variable

As long as there's no write access to this variable there's no reason 
to let gcc check it at runtime.

Signed-off-by: Adrian Bunk <bunk@...sta.de>

---

This patch has been sent on:
- 6 Jul 2007

 arch/i386/kernel/topology.c |    2 --
 include/asm-i386/cpu.h      |    2 +-
 2 files changed, 1 insertion(+), 3 deletions(-)

--- linux-2.6.22-rc6-mm1/include/asm-i386/cpu.h.old	2007-07-04 20:29:25.000000000 +0200
+++ linux-2.6.22-rc6-mm1/include/asm-i386/cpu.h	2007-07-04 20:36:33.000000000 +0200
@@ -13,7 +13,7 @@
 extern int arch_register_cpu(int num);
 #ifdef CONFIG_HOTPLUG_CPU
 extern void arch_unregister_cpu(int);
-extern int enable_cpu_hotplug;
+#define enable_cpu_hotplug	1
 #else
 #define enable_cpu_hotplug	0
 #endif
--- linux-2.6.22-rc6-mm1/arch/i386/kernel/topology.c.old	2007-07-04 20:30:12.000000000 +0200
+++ linux-2.6.22-rc6-mm1/arch/i386/kernel/topology.c	2007-07-04 20:35:56.000000000 +0200
@@ -51,8 +51,6 @@
 }
 
 #ifdef CONFIG_HOTPLUG_CPU
-int enable_cpu_hotplug = 1;
-
 void arch_unregister_cpu(int num) {
 	return unregister_cpu(&cpu_devices[num].cpu);
 }

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ