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>, Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH 2/2] deal with interrupt shadow state for emulated instruction
Date: Tue, 12 May 2009 21:14:40 +0300 [thread overview]
Message-ID: <4A09BC90.9030700@redhat.com> (raw)
In-Reply-To: <1242141230-22514-3-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.
>
> 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
>
> @@ -1618,6 +1620,15 @@ special_insn:
> int err;
>
> sel = c->src.val;
> + if (c->modrm_reg == VCPU_SREG_SS) {
> + u32 int_shadow =
> + kvm_x86_ops->get_interrupt_shadow(ctxt->vcpu,
> + X86_SHADOW_INT_MOV_SS);
> + /* See sti emulation for an explanation of this */
> + if (!(int_shadow & X86_SHADOW_INT_MOV_SS))
> + ctxt->interruptibility = X86_SHADOW_INT_MOV_SS;
> + }
>
The indentation of the first statement here is annoying. Suggest a
function toggle_interruptibility(ctxt, mask). Would eliminate the need
for the comment forward reference as well.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-05-12 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-12 15:13 [PATCH 0/2] Deal with shadow interrupts after emulated instructions Glauber Costa
2009-05-12 15:13 ` [PATCH 1/2] replace drop_interrupt_shadow by set_interrupt_shadow Glauber Costa
2009-05-12 15:13 ` [PATCH 2/2] deal with interrupt shadow state for emulated instruction Glauber Costa
2009-05-12 18:14 ` Avi Kivity [this message]
2009-05-12 18:11 ` [PATCH 1/2] replace drop_interrupt_shadow by set_interrupt_shadow Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 20:21 [PATCH 0/2] Deal with shadow interrupts after emulated instructions Glauber Costa
2009-05-12 20:21 ` [PATCH 1/2] replace drop_interrupt_shadow by set_interrupt_shadow Glauber Costa
2009-05-12 20:21 ` [PATCH 2/2] deal with interrupt shadow state for emulated instruction Glauber Costa
2009-05-08 20:23 [PATCH 0/2] Deal with shadow interrupts after emulated instructions Glauber Costa
2009-05-08 20:23 ` [PATCH 1/2] replace drop_interrupt_shadow by set_interrupt_shadow Glauber Costa
2009-05-08 20:23 ` [PATCH 2/2] deal with interrupt shadow state for emulated instruction Glauber Costa
2009-05-10 13:09 ` Avi Kivity
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=4A09BC90.9030700@redhat.com \
--to=avi@redhat.com \
--cc=gleb@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.