From: Avi Kivity <avi@qumranet.com>
To: Laurent Vivier <Laurent.Vivier@bull.net>
Cc: kvm@vger.kernel.org, Stefan Hajnoczi <stefanha@gmail.com>
Subject: Re: [PATCH] Clear temporary interrupt blocking on halt in real mode
Date: Sun, 10 Aug 2008 11:36:08 +0300 [thread overview]
Message-ID: <489EA878.4040503@qumranet.com> (raw)
In-Reply-To: <12179254282930-git-send-email-Laurent.Vivier@bull.net>
Laurent Vivier wrote:
> When "halt" is emulated, skip_emulated_instruction() is called and interruptibility state is cleared.
> But when halt is emulated in real mode, skip_emulated_instruction() is not called and the interruptiblity state is not cleared.
>
> The following code, from gPXE, never exits from loop because interrupts are not delivered to increase %fs:(0x6c):
>
> movl %fs:(0x6c), %eax
> 1: pushf
> sti
> hlt
> popf
> cmpl %fs:(0x6c), %eax
> je 1b
>
> This patch clears the interruptibility state when halt is emulated in real mode.
>
> Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net>
> ---
> arch/x86/kvm/vmx.c | 10 ++++++++++
> 1 files changed, 10 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index c4510fe..82c4324 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -2329,7 +2329,17 @@ static int handle_exception(struct kvm_vcpu *vcpu, struct kvm_run *kvm_run)
> handle_rmode_exception(vcpu, intr_info & INTR_INFO_VECTOR_MASK,
> error_code)) {
> if (vcpu->arch.halt_request) {
> + u32 interruptibility;
> vcpu->arch.halt_request = 0;
> + /*
> + * We emulated an instruction, so temporary interrupt blocking
> + * should be removed, if set.
> + */
> + interruptibility = vmcs_read32(GUEST_INTERRUPTIBILITY_INFO);
> + if (interruptibility & 3)
> + vmcs_write32(GUEST_INTERRUPTIBILITY_INFO,
> + interruptibility & ~3);
> + vcpu->arch.interrupt_window_open = 1;
> return kvm_emulate_halt(vcpu);
> }
> return 1;
>
Shouldn't interruptibility state be cleared if *any* instruction is
emulated?
(of course, an emulated instruction may update interruptibility state
itself, say sti).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-08-10 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 8:37 [PATCH] Clear temporary interrupt blocking on halt in real mode Laurent Vivier
2008-08-10 8:36 ` Avi Kivity [this message]
2008-09-04 15:51 ` Laurent Vivier
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=489EA878.4040503@qumranet.com \
--to=avi@qumranet.com \
--cc=Laurent.Vivier@bull.net \
--cc=kvm@vger.kernel.org \
--cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.