Displaying 3 results from an estimated 3 matches for "nmi_watchdog_tick".
2006 Jul 31
1
x86_64 reproducible server PANIC with latest kernel
...00000000013
0000000000000000 0000000000000046 0000000000029bd5 0000000000000046
0000000000000004 ffffffff8031fad8
Call Trace:<ffffffff80111860>{show_stack+241}
<ffffffff8011198a>{show_registers+277}
<ffffffff80111c91>{die_nmi+130}
<ffffffff8011d055>{nmi_watchdog_tick+210}
<ffffffff8011255e>{default_do_nmi+112}
<ffffffff8011d10b>{do_nmi+115}
<ffffffff80111173>{paranoid_exit+0}
<ffffffff8030a9aa>{.text.lock.spinlock+46}
<ffffffff8013b98a>{it_real_fn+0} <ffffffff8013b98a>{it_real_fn+0}
Code: 0f 0b dd...
2012 Nov 14
0
[PATCH] x86/nmi: self_nmi() should not unconditionally enable interrupts
...rrupts enabled, making the
code currently safe but dangerous. Also, fix a trailing whitespace issue.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
diff -r 8b93ac0c93f3 -r f3adcb7d84ea xen/arch/x86/nmi.c
--- a/xen/arch/x86/nmi.c
+++ b/xen/arch/x86/nmi.c
@@ -482,13 +482,14 @@ void nmi_watchdog_tick(struct cpu_user_r
* 8-3 and 8-4 in IA32 Reference Manual Volume 3. We send the IPI to
* our own APIC ID explicitly which is valid.
*/
-void self_nmi(void)
+void self_nmi(void)
{
+ unsigned long flags;
u32 id = get_apic_id();
- local_irq_disable();
+ local_irq_save(flags);...
2012 Nov 22
41
[PATCH V3] vmx/nmi: Do not use self_nmi() in VMEXIT handler
The self_nmi() code cause''s an NMI to be triggered by sending an APIC
message to the local processor. However, NMIs are blocked by the
VMEXIT, until the next iret or VMENTER.
Volume 3 Chapter 27 Section 1 of the Intel SDM states:
An NMI causes subsequent NMIs to be blocked, but only after the VM exit
completes.
As a result, as soon as the VMENTER happens, an immediate VMEXIT
happens