linux.git/arch/i386/kernel/cpu, branch master

i386: move kernel/cpu

2007-10-11T09:16:58+00:00

Signed-off-by: Thomas Gleixner 
Signed-off-by: Ingo Molnar

i386: move kernel/cpu/mtrr

2007-10-11T09:16:28+00:00

Signed-off-by: Thomas Gleixner 
Signed-off-by: Ingo Molnar

i386: move kernel/cpu/cpufreq

2007-10-11T09:16:27+00:00

Signed-off-by: Thomas Gleixner 
Signed-off-by: Ingo Molnar

i386: move kernel/cpu/mcheck

2007-10-11T09:16:25+00:00

Signed-off-by: Thomas Gleixner 
Signed-off-by: Ingo Molnar

Longhaul: add auto enabled "revid_errata" option

2007-10-07T23:28:43+00:00

VIA C3 Ezra-T has RevisionID equal to 1, but it needs RevisionKey to be 0
or CPU will ignore new frequency and will continue to work at old
frequency.  New "revid_errata" option will force RevisionKey to be set to
0, whatever RevisionID is.

Additionaly "Longhaul" will not silently ignore unsuccessful transition.
It will try to check if "revid_errata" or "disable_acpi_c3" options need to
be enabled for this processor/system.

Same for Longhaul ver.  2 support.  It will be disabled if none of above
options will work.

 Best case scenario (with patch apllied and v2 enabled):
 longhaul: VIA C3 'Ezra' [C5C] CPU detected.  Longhaul v2 supported.
 longhaul: Using northbridge support.
 longhaul: VRM 8.5
 longhaul: Max VID=1.350  Min VID=1.050, 13 possible voltage scales
 longhaul: f: 300000 kHz, index: 0, vid: 1050 mV
 [...]
 longhaul: Voltage scaling enabled.
 Worst case scenario:
 longhaul: VIA C3 'Ezra-T' [C5M] CPU detected.  Powersaver supported.
 longhaul: Using northbridge support.
 longhaul: Using ACPI support.
 longhaul: VRM 8.5
 longhaul: Claims to support voltage scaling but min & max are both 1.250. Voltage scaling disabled
 longhaul: Failed to set requested frequency!
 longhaul: Enabling "Ignore Revision ID" option.
 longhaul: Failed to set requested frequency!
 longhaul: Disabling ACPI C3 support.
 longhaul: Disabling "Ignore Revision ID" option.
 longhaul: Failed to set requested frequency!
 longhaul: Enabling "Ignore Revision ID" option.

[akpm@linux-foundation.org: coding-style cleanups]
Signed-off-by: Rafal Bilski 
Signed-off-by: Dave Jones 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

x86_64: Prevent doing anything from cache_remove_dev() when info setup failed.

2007-09-12T16:28:06+00:00

AK: Removed the unlikelies because gcc heuristics default to unlikely
AK: for test == NULL and for negative returns.

Cc: Venkatesh Pallipadi 
Cc: Ashok Raj 
Cc: Akinobu Mita 
Signed-off-by: Jan Beulich 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

i386: Fix perfctr watchdog on core duo

2007-09-11T01:57:47+00:00

Fix the NMI watchdog on Intel CoreDuo processor where the kernel would
get stuck during boot.  The issue is related to errata AE49, where the
PERFEVTSEL1 counter does not have a working enable bit.  Thus it is not
possible to use it for NMI.

The patch creates a dedicated wd_ops for CoreDuo which falls back to
using PERFEVTSEL0.  The other Intel processors supporting the
architectural PMU will keep on using PERFEVTSEL1 as this allows other
subsystems, such as perfmon, to use PERFEVTSEL0 for PEBS monitoring in
particular.  Bug initially reported by Daniel Walker.

AK: Added comments

Signed-off-by: Stephane Eranian 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

Pull processor into release branch

2007-08-12T04:21:08+00:00

i386: Use global flag to disable broken local apic timer on AMD CPUs.

2007-08-11T22:58:13+00:00

The Averatec 2370 and some other Turion laptop BIOS seems to program the
ENABLE_C1E MSR inconsistently between cores. This confuses the lapic
use heuristics because when C1E is enabled anywhere it seems to affect
the complete chip.

Use a global flag instead of a per cpu flag to handle this.
If any CPU has C1E enabled disabled lapic use.

Thanks to Cal Peake for debugging.

Cc: tglx@linutronix.de
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds

acpi-cpufreq: Fix some x86/x86-64 acpi-cpufreq driver issues

2007-08-07T22:40:30+00:00

This patch addresses some issues in x86/x86-64 acpi-cpufreq driver:

1.  Current memory allocation for acpi_perf_data is actually open-coded
   alloc_percpu().  The patch defines and handles acpi_perf_data as percpu
   data.  The code will be cleaner and easier to be maintained with this
   change.

2. Won't load driver in acpi_cpufreq_early_init() failure case.

3. Add __init for acpi_cpufreq_early_init().

Signed-off-by: Fenghua Yu 
Acked-by: Venkatesh Pallipadi 
Cc: Dave Jones 
Signed-off-by: Andrew Morton 
Signed-off-by: Len Brown