diff options
author | Venkatesh Pallipadi <venki@google.com> | 2010-05-18 14:39:16 -0700 |
---|---|---|
committer | Len Brown <len.brown@intel.com> | 2010-05-28 15:34:57 -0400 |
commit | 0dc698b93f3eecdda43b22232131324eb41e510c (patch) | |
tree | 5eff6780615220931c8d86f9ce7f337dd4443904 /include/acpi | |
parent | b6fecaa8685a9922d11db2cd79e76f43c3edc970 (diff) | |
download | linux-3.10-0dc698b93f3eecdda43b22232131324eb41e510c.tar.gz linux-3.10-0dc698b93f3eecdda43b22232131324eb41e510c.tar.bz2 linux-3.10-0dc698b93f3eecdda43b22232131324eb41e510c.zip |
ACPI: Don't let acpi_pad needlessly mark TSC unstable
acpi pad driver kind of aggressively marks TSC as unstable at init
time, on mwait capable and non X86_FEATURE_NONSTOP_TSC systems. This is
irrespective of whether pad driver is ever going to be used on the
system or deep C-states are supported/used. This will affect every user
who just happens to compile in (or get a kernel version which
compiles in) acpi pad driver.
Move mark_tsc_unstable() out of init to the actual idle invocation path
of the pad driver.
There is also another bug/missing_feature in the code that it does not
support 'always running apic timer' and switches to broadcast mode
unconditionally. Shaohua, can you take a look at that please.
Signed-off-by: Venkatesh Pallipadi <venki@google.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'include/acpi')
0 files changed, 0 insertions, 0 deletions