From: "H. Peter Anvin" <hpa@zytor.com>
To: Avi Kivity <avi@redhat.com>
Cc: Glauber Costa <glommer@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deal with interrupt shadow state for emulated instruction
Date: Sat, 11 Apr 2009 14:15:50 -0700 [thread overview]
Message-ID: <49E10886.8010101@zytor.com> (raw)
In-Reply-To: <49E0C767.8060603@redhat.com>
Avi Kivity wrote:
>>
>> - 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.
>
Not at architecturally visible boundaries, for sure. It can be an
implementation artifact internally to an instruction, though.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-04-11 21:16 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
2009-04-11 21:15 ` H. Peter Anvin [this message]
-- 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=49E10886.8010101@zytor.com \
--to=hpa@zytor.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.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.