On Fri, 2008-06-20 at 03:14 -0400, Len Brown wrote: > > I notice on the T61 that this disables MWAIT for C2 and C3, > but not for C1. > > While I know that the issue at hand is C2 and C3, > it seems misleading to boot with idle=nomwait > and see that MWAIT is used for C1. What you said is correct. The description is not appropriate.Maybe the following title will be appropriate. >Add boot option of "idle=nomwait" to disable mwait for CPU C2/C3 The boot option of "idle=nomwait" will disable mwait for CPU C2/C3 and still use mwait for C1 if mwait is supported. In fact we only hope to disable mwait for CPU C2/C3 on some broken system by adding this boot option. Thanks. > I think we should extend this param to also apply > to the MWAIT use for C1. I don't think the difference > between MWAIT and HALT in C1 will be signficant, given > that this is a debugging-tool/bug workaround. > > thanks, > -Len > > [lenb@t61 ~]$ grep . /sys/devices/system/cpu/cpu*/cpuidle/*/* > /sys/devices/system/cpu/cpu0/cpuidle/state0/desc:<null> > /sys/devices/system/cpu/cpu0/cpuidle/state0/latency:0 > /sys/devices/system/cpu/cpu0/cpuidle/state0/name:<null> > /sys/devices/system/cpu/cpu0/cpuidle/state0/power:4294967295 > /sys/devices/system/cpu/cpu0/cpuidle/state0/time:24103 > /sys/devices/system/cpu/cpu0/cpuidle/state0/usage:27 > /sys/devices/system/cpu/cpu0/cpuidle/state1/desc:ACPI FFH INTEL MWAIT 0x0 > /sys/devices/system/cpu/cpu0/cpuidle/state1/latency:1 > /sys/devices/system/cpu/cpu0/cpuidle/state1/name:C1 > /sys/devices/system/cpu/cpu0/cpuidle/state1/power:1000 > /sys/devices/system/cpu/cpu0/cpuidle/state1/time:0 > /sys/devices/system/cpu/cpu0/cpuidle/state1/usage:0 > /sys/devices/system/cpu/cpu0/cpuidle/state2/desc:ACPI IOPORT 0x1014 > /sys/devices/system/cpu/cpu0/cpuidle/state2/latency:1 > /sys/devices/system/cpu/cpu0/cpuidle/state2/name:C2 > /sys/devices/system/cpu/cpu0/cpuidle/state2/power:500 > /sys/devices/system/cpu/cpu0/cpuidle/state2/time:21905 > /sys/devices/system/cpu/cpu0/cpuidle/state2/usage:569 > /sys/devices/system/cpu/cpu0/cpuidle/state3/desc:ACPI IOPORT 0x1015 > /sys/devices/system/cpu/cpu0/cpuidle/state3/latency:17 > /sys/devices/system/cpu/cpu0/cpuidle/state3/name:C3 > /sys/devices/system/cpu/cpu0/cpuidle/state3/power:250 > /sys/devices/system/cpu/cpu0/cpuidle/state3/time:284208055 > /sys/devices/system/cpu/cpu0/cpuidle/state3/usage:53661 > /sys/devices/system/cpu/cpu1/cpuidle/state0/desc:<null> > /sys/devices/system/cpu/cpu1/cpuidle/state0/latency:0 > /sys/devices/system/cpu/cpu1/cpuidle/state0/name:<null> > /sys/devices/system/cpu/cpu1/cpuidle/state0/power:4294967295 > /sys/devices/system/cpu/cpu1/cpuidle/state0/time:237647 > /sys/devices/system/cpu/cpu1/cpuidle/state0/usage:25 > /sys/devices/system/cpu/cpu1/cpuidle/state1/desc:ACPI FFH INTEL MWAIT 0x0 > /sys/devices/system/cpu/cpu1/cpuidle/state1/latency:1 > /sys/devices/system/cpu/cpu1/cpuidle/state1/name:C1 > /sys/devices/system/cpu/cpu1/cpuidle/state1/power:1000 > /sys/devices/system/cpu/cpu1/cpuidle/state1/time:0 > /sys/devices/system/cpu/cpu1/cpuidle/state1/usage:0 > /sys/devices/system/cpu/cpu1/cpuidle/state2/desc:ACPI IOPORT 0x1014 > /sys/devices/system/cpu/cpu1/cpuidle/state2/latency:1 > /sys/devices/system/cpu/cpu1/cpuidle/state2/name:C2 > /sys/devices/system/cpu/cpu1/cpuidle/state2/power:500 > /sys/devices/system/cpu/cpu1/cpuidle/state2/time:32354 > /sys/devices/system/cpu/cpu1/cpuidle/state2/usage:1042 > /sys/devices/system/cpu/cpu1/cpuidle/state3/desc:ACPI IOPORT 0x1015 > /sys/devices/system/cpu/cpu1/cpuidle/state3/latency:17 > /sys/devices/system/cpu/cpu1/cpuidle/state3/name:C3 > /sys/devices/system/cpu/cpu1/cpuidle/state3/power:250 > /sys/devices/system/cpu/cpu1/cpuidle/state3/time:294127944 > /sys/devices/system/cpu/cpu1/cpuidle/state3/usage:65794 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-acpi" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html