From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] deal with interrupt shadow state for emulated instruction
Date: Sat, 11 Apr 2009 19:37:59 +0300 [thread overview]
Message-ID: <49E0C767.8060603@redhat.com> (raw)
In-Reply-To: <1239226966-8205-1-git-send-email-glommer@redhat.com>
Glauber Costa wrote:
> we currently unblock shadow interrupt state when we skip an instruction,
> but failing to do so when we actually emulate one. This blocks interrupts
> in key instruction blocks, in particular sti; hlt; sequences
>
> If the instruction emulated is an sti, we have to block shadow interrupts.
> The same goes for mov ss. pop ss also needs it, but we don't currently
> emulate it. For sequences of two or more instructions of the same type
> among those instructions, only the first one has this effect.
>
> Without this patch, I cannot boot gpxe option roms at vmx machines.
> This is described at https://bugzilla.redhat.com/show_bug.cgi?id=494469
>
> --- a/arch/x86/include/asm/kvm_host.h
> +++ b/arch/x86/include/asm/kvm_host.h
> @@ -513,6 +513,8 @@ struct kvm_x86_ops {
> void (*run)(struct kvm_vcpu *vcpu, struct kvm_run *run);
> int (*handle_exit)(struct kvm_run *run, struct kvm_vcpu *vcpu);
> void (*skip_emulated_instruction)(struct kvm_vcpu *vcpu);
> + void (*block_interrupt_shadow)(struct kvm_vcpu *vcpu);
> + void (*unblock_interrupt_shadow)(struct kvm_vcpu *vcpu);
>
set_interrupt_shadow(), clear_interrupt_shadow(). The interrupt shadow
blocks interrupts, but what happens when you block the interrupt shadow?
Maybe better to fold into one callback with a parameter.
> int x86_emulate_insn(struct x86_emulate_ctxt *ctxt,
> - struct x86_emulate_ops *ops);
> + struct x86_emulate_ops *ops, int *interruptibility);
>
Add to x86_emulate_ctxt, there's already some
>
> +static void svm_block_interrupt_shadow(struct kvm_vcpu *vcpu)
> +{
> + struct vcpu_svm *svm = to_svm(vcpu);
> +
> + svm->vmcb->control.int_state |= SVM_INTERRUPT_SHADOW_MASK;
> + vcpu->arch.interrupt_window_open = 0;
> +}
> +
> +static void svm_unblock_interrupt_shadow(struct kvm_vcpu *vcpu)
> +{
> + struct vcpu_svm *svm = to_svm(vcpu);
> +
> + svm->vmcb->control.int_state &= ~SVM_INTERRUPT_SHADOW_MASK;
> + vcpu->arch.interrupt_window_open = (svm->vcpu.arch.hflags & HF_GIF_MASK);
>
If eflags.if = 0, the interrupt window is closed.
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index c6997c0..5158c2b 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -736,26 +736,45 @@ static void vmx_set_rflags(struct kvm_vcpu *vcpu, unsigned long rflags)
> vmcs_writel(GUEST_RFLAGS, rflags);
> }
>
> -static void skip_emulated_instruction(struct kvm_vcpu *vcpu)
> +static void vmx_block_interrupt_shadow(struct kvm_vcpu *vcpu)
> {
> - unsigned long rip;
> - u32 interruptibility;
> + u32 interruptibility = vmcs_read32(GUEST_INTERRUPTIBILITY_INFO);
> + u32 interruptibility_mask = ((GUEST_INTR_STATE_STI | GUEST_INTR_STATE_MOV_SS));
>
> - rip = kvm_rip_read(vcpu);
> - rip += vmcs_read32(VM_EXIT_INSTRUCTION_LEN);
> - kvm_rip_write(vcpu, rip);
> + if (!(interruptibility & interruptibility_mask))
> + vmcs_write32(GUEST_INTERRUPTIBILITY_INFO,
> + interruptibility | interruptibility_mask);
> + vcpu->arch.interrupt_window_open = 0;
>
Setting both _MOV_SS and _STI is wierd; can't happen on real hardware.
> {
> unsigned long memop = 0;
> u64 msr_data;
> @@ -1359,6 +1360,10 @@ x86_emulate_insn(struct x86_emulate_ctxt *ctxt, struct x86_emulate_ops *ops)
> unsigned int port;
> int io_dir_in;
> int rc = 0;
> + static int movss_int_flag, movss_int_flag_old;
>
static, for shame.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2009-04-11 16:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 21:42 [PATCH] deal with interrupt shadow state for emulated instruction Glauber Costa
2009-04-11 16:37 ` Avi Kivity [this message]
2009-04-11 21:15 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2009-04-13 20:06 Glauber Costa
2009-04-14 9:07 ` Gleb Natapov
2009-04-14 9:34 ` Avi Kivity
2009-04-14 16:07 ` H. Peter Anvin
2009-04-14 16:14 ` Avi Kivity
2009-04-14 16:25 ` H. Peter Anvin
2009-04-16 9:18 ` Avi Kivity
2009-04-16 22:40 ` H. Peter Anvin
2009-04-19 8:26 ` Avi Kivity
2009-04-14 17:31 ` Alan Cox
2009-04-14 17:32 ` H. Peter Anvin
2009-04-28 14:30 Glauber Costa
2009-04-30 11:50 ` Avi Kivity
2009-05-05 13:57 ` Glauber Costa
2009-05-05 18:40 Glauber Costa
2009-05-06 8:03 ` Gleb Natapov
2009-05-06 10:51 ` Avi Kivity
2009-05-08 5:25 ` Glauber Costa
2009-05-08 7:18 ` Gleb Natapov
2009-05-08 13:02 ` Glauber Costa
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=49E0C767.8060603@redhat.com \
--to=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.