kernel.git/arch/x86/kernel/cpu/mcheck, branch linux-2.6.30.y

KVM: Add VT-x machine check support v4

2009-07-02T23:49:32Z

(replaces commit a0861c02a981c943573478ea13b29b1fb958ee5b upstream in a cleaner way for the 2.6.30 kernel tree) VT-x needs an explicit MC vector intercept to handle machine checks in the hypervisor. It also has a special option to catch machine checks that happen during VT entry. Do these interceptions and forward them to the Linux machine check handler. Make it always look like user space is interrupted because the machine check handler treats kernel/user space differently. Thanks to Huang Ying and Jiang Yunhong for help and testing. Cc: ying.huang@intel.com v2: Handle machine checks still in interrupt off context to avoid problems on preemptible kernels. v3: Handle old style 32bit and make fully standalone Signed-off-by: Andi Kleen Cc: Huang Ying Acked-by: Avi Kivity Signed-off-by: Greg Kroah-Hartman

cpumask: alloc zeroed cpumask for static cpumask_var_ts

2009-06-09T13:00:27Z

These are defined as static cpumask_var_t so if MAXSMP is not used, they are cleared already. Avoid surprises when MAXSMP is enabled. Signed-off-by: Yinghai Lu Signed-off-by: Rusty Russell

x86: MCE: make cmci_discover_lock irq-safe

2009-05-08T09:03:26Z

Lockdep reports the warning below when Li tries to offline one cpu: [ 110.835487] ================================= [ 110.835616] [ INFO: inconsistent lock state ] [ 110.835688] 2.6.30-rc4-00336-g8c9ed89 #52 [ 110.835757] --------------------------------- [ 110.835828] inconsistent {HARDIRQ-ON-W} -> {IN-HARDIRQ-W} usage. [ 110.835908] swapper/0 [HC1[1]:SC0[0]:HE0:SE1] takes: [ 110.835982] (cmci_discover_lock){?.+...}, at: [] cmci_clear+0x30/0x9b cmci_clear() can be called via smp_call_function_single(). It is better to disable interrupt while holding cmci_discover_lock, to turn it into an irq-safe lock - we can deadlock otherwise. [ Impact: fix possible deadlock in the MCE code ] Reported-by: Shaohua Li Signed-off-by: Hidetoshi Seto Cc: Andi Kleen Cc: Andrew Morton LKML-Reference: <4A03ED38.8000700@jp.fujitsu.com> Signed-off-by: Ingo Molnar Reported-by: Shaohua Li

x86, mce: fix boot logging logic

2009-04-22T20:56:25Z

The earlier patch to change the poller to a separate function subtly broke the boot logging logic. This could lead to machine checks getting logged at boot even when disabled or defaulting to off on some systems. Fix that. [ Impact: bug fix - avoid spurious MCE in log ] Signed-off-by: Andi Kleen Reviewed-by: Hidetoshi Seto Signed-off-by: H. Peter Anvin

x86, mce: make polling timer interval per CPU

2009-04-22T20:54:37Z

The polling timer while running per CPU still uses a global next_interval variable, which lead to some CPUs either polling too fast or too slow. This was not a serious problem because all errors get picked up eventually, but it's still better to avoid it. Turn next_interval into a per cpu variable. v2: Fix check_interval == 0 case (Hidetoshi Seto) [ Impact: minor bug fix ] Signed-off-by: Andi Kleen Reviewed-by: Hidetoshi Seto Signed-off-by: H. Peter Anvin

Merge branch 'linus' into cpumask-for-linus

2009-03-30T21:53:32Z

Conflicts: arch/x86/kernel/cpu/common.c

x86: use smp_call_function_single() in arch/x86/kernel/cpu/mcheck/mce_amd_64.c

2009-03-18T06:03:12Z

Attempting to rid us of the problematic work_on_cpu(). Just use smp_call_function_single() here. Signed-off-by: Andrew Morton Signed-off-by: Rusty Russell LKML-Reference: <20090318042217.EF3F1DDF39@ozlabs.org> Signed-off-by: Ingo Molnar

x86, mce: remove incorrect __cpuinit for intel_init_cmci()

2009-03-16T08:15:32Z

Impact: Bug fix on UP Referring commit cc3ca22063784076bd240fda87217387a8f2ae92, Peter removed __cpuinit annotations for mce_cpu_features() and its successor functions, which caused troubles on UP configurations. However the intel_init_cmci() was introduced after that and it also has __cpuinit annotation even though it is called from mce_cpu_features(). Remove the annotation from that function too. Signed-off-by: Hidetoshi Seto Cc: H. Peter Anvin Cc: Andi Kleen Signed-off-by: Ingo Molnar

cpumask: use new cpumask functions throughout x86

2009-03-13T04:19:54Z

Impact: cleanup 1) &cpu_online_map -> cpu_online_mask 2) first_cpu/next_cpu_nr -> cpumask_first/cpumask_next 3) cpu_*_map manipulation -> init_cpu_* / set_cpu_* Signed-off-by: Rusty Russell

cpumask: convert arch/x86/kernel/cpu/mcheck/mce_64.c

2009-03-13T04:19:51Z

Impact: reduce kernel memory usage when CONFIG_CPUMASK_OFFSTACK=y Simple conversion of mce_device_initialized to cpumask_var_t. We don't check the alloc_cpumask_var() return since it's boot-time only, and the misc_register() in that same function isn't checked. Signed-off-by: Rusty Russell