Len, is there any good reason why max_cstate was made invisible in 2.6.24,
breaking my userspace scripts that access it?
Here's a patch to fix the regression from 2.6.23:
Restore visibility of /sys/module/processor/parameters/max_cstate
for compatibility with kernels prior to 2.6.24.
I have scripts here that rely upon it.
Signed-off-by: Mark Lord <[EMAIL PROTECTED]>
---
Patch is against 2.6.24-rc3-git5.
--- linux/drivers/acpi/processor_idle.c.orig 2007-11-30 13:35:20.000000000
-0500
+++ linux/drivers/acpi/processor_idle.c 2007-11-30 13:35:31.000000000 -0500
@@ -76,7 +76,7 @@
#define PM_TIMER_TICKS_TO_US(p) (((p) * 1000)/(PM_TIMER_FREQUENCY/1000))
static unsigned int max_cstate __read_mostly = ACPI_PROCESSOR_MAX_POWER;
-module_param(max_cstate, uint, 0000);
+module_param(max_cstate, uint, 0644);
static unsigned int nocst __read_mostly;
module_param(nocst, uint, 0000);
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
