From: Jan Kiszka <jan.kiszka@web.de>
To: Arthur Chunqi Li <yzt356@gmail.com>, kvm <kvm@vger.kernel.org>
Subject: Re: Handle multiple interrupts injection in one vmexit
Date: Mon, 26 May 2014 18:44:19 +0800 [thread overview]
Message-ID: <53831B03.4010505@web.de> (raw)
In-Reply-To: <CABpY8M+4v04y+G5OkLekTRGnQfifiQFcDnrEKQNwq71nnkNfHQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
On 2014-05-26 15:51, Arthur Chunqi Li wrote:
> Hi there,
>
> External interrupts are injected in function vcpu_enter_guest, with
> checking KVM_REQ_EVENT. If there are more than one interrupts in one
> vmexit (e.g. nmi and external events occur concurrently in one
> vmexit), KVM will handle only one interrupt of the highest priority
> (e.g. NMI), right? So only NMI is injected in this vmexit, thus when
> will the other external events injected? I don't see any extra setting
> of KVM_REQ_EVENT to handle the lower priority interrupts injection in
> KVM.
[you should mention that you are talking about x86 here]
If both events are pending, inject_pending_event will try to inject the
NMI. vcpu_enter_guest will then notice that there are still pending
interrupts and request the interrupt window vmexit. If the NMI should be
blocked, an NMI window exit is requested. But on NMI injection, another
KVM_REQ_EVENT is send (see e.g. handle_nmi_window in vmx.c).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2014-05-26 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 7:51 Handle multiple interrupts injection in one vmexit Arthur Chunqi Li
2014-05-26 10:44 ` Jan Kiszka [this message]
2014-05-26 11:09 ` Arthur Chunqi Li
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=53831B03.4010505@web.de \
--to=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=yzt356@gmail.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