[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <67e90d97e0a77df4acd0c75e1bacc7714e011f3e.1301550524.git.len.brown@intel.com>
Date: Thu, 31 Mar 2011 02:03:16 -0400
From: Len Brown <lenb@...nel.org>
To: x86@...nel.org
Cc: linux-kernel@...r.kernel.org, linux-pm@...ts.linux-foundation.org,
Len Brown <len.brown@...el.com>
Subject: [PATCH 1/9] x86 idle: remove "no-hlt" cmdline param
From: Len Brown <len.brown@...el.com>
The X86_32-only "no-hlt" option was the functional equivalent of
"idle=poll" for the idle loop.
It would also set the X86_32-only "hlt_bug" line in the /proc/cpuinfo,
and cause halt to be skipped in stop_this_cpu().
Signed-off-by: Len Brown <len.brown@...el.com>
---
Documentation/kernel-parameters.txt | 4 ----
arch/x86/kernel/cpu/bugs.c | 8 --------
2 files changed, 0 insertions(+), 12 deletions(-)
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index f4a04c0..e6b4843 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -1666,10 +1666,6 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
wfi(ARM) instruction doesn't work correctly and not to
use it. This is also useful when using JTAG debugger.
- no-hlt [BUGS=X86-32] Tells the kernel that the hlt
- instruction doesn't work correctly and not to
- use it.
-
no_file_caps Tells the kernel not to honor file capabilities. The
only way then for a file to be executed with privilege
is to be setuid root or executed by root.
diff --git a/arch/x86/kernel/cpu/bugs.c b/arch/x86/kernel/cpu/bugs.c
index c39576c..4c91631 100644
--- a/arch/x86/kernel/cpu/bugs.c
+++ b/arch/x86/kernel/cpu/bugs.c
@@ -17,14 +17,6 @@
#include <asm/paravirt.h>
#include <asm/alternative.h>
-static int __init no_halt(char *s)
-{
- boot_cpu_data.hlt_works_ok = 0;
- return 1;
-}
-
-__setup("no-hlt", no_halt);
-
static int __init no_387(char *s)
{
boot_cpu_data.hard_math = 0;
--
1.7.4.2.406.gbe91
--
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