From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>,
"Xu, Jiajun" <jiajun.xu@intel.com>,
"Yang, Sheng" <sheng.yang@intel.com>,
Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] KVM: VMX: Fix race between pending IRQ and NMI
Date: Wed, 19 Nov 2008 23:28:52 +0200 [thread overview]
Message-ID: <49248514.9020605@redhat.com> (raw)
In-Reply-To: <49244F20.3030803@redhat.com>
Avi Kivity wrote:
> Jan Kiszka wrote:
>> Jiajun kindly provided me a RHEL kernel and initrd (2.6.18-53-el5) which
>> I ran for a while (or booted a few times) to trigger the hang. Basically
>> you need high IRQ load (preferably via LAPIC, to exploit that un-acked
>> IRQs will block low-prio IRQs as well) + high NMI load (e.g. via NMI
>> watchdog).
>>
>
> I was able to reproduce it easily by zapping the mmu every second.
>
> Attached is a patch the fixes it for me. Basically it avoids the nmi
> path if an interrupt is being injected. This is closer to my event
> queue plan, and also is similar to what the code does today with
> exceptions (avoid ->inject_pending_irq() if an exception is pending).
>
Oh, and I think this is more correct than the previous approach of
letting the nmi preempt the interrupt.
The nmi handler could change the tpr to mask the preempted interrupt;
but the code would not notice that. Once the interrupt was injected the
guest would see an interrupt at a higher priority than it has programmed
the hardware to allow.
Basically, once we commit to an interrupt via kvm_cpu_get_interrupt(),
we must inject it before the any instruction gets executed.
I don't think any real guest would notice, though.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2008-11-19 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 15:52 [PATCH] KVM: VMX: Fix race between pending IRQ and NMI Jan Kiszka
2008-11-16 12:29 ` Avi Kivity
2008-11-16 14:58 ` Jan Kiszka
2008-11-16 15:15 ` Avi Kivity
2008-11-16 15:39 ` Jan Kiszka
2008-11-19 17:38 ` Avi Kivity
2008-11-19 21:28 ` Avi Kivity [this message]
2008-11-20 13:29 ` Jan Kiszka
2008-11-20 13:59 ` Avi Kivity
2008-11-21 10:04 ` Jan Kiszka
2008-11-21 11:14 ` Avi Kivity
2008-11-22 12:25 ` Avi Kivity
2008-11-24 9:55 ` Jan Kiszka
2008-11-25 14:45 ` Avi Kivity
2008-11-25 14:55 ` Jan Kiszka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49248514.9020605@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jan.kiszka@web.de \
--cc=jiajun.xu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=sheng.yang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox