From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: FW: [kvm-commits] KVM: Move interrupt injection out of interruptdisabled section
Date: Fri, 26 Oct 2007 12:13:57 +0200 [thread overview]
Message-ID: <4721BDE5.4030308@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A02482C1C-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
Dong, Eddie wrote:
>> I didn't see anything in 20.8.3 regarding injection of software
>> interrupts to vm86 mode. And other sections in the manual (22.5.1)
>> imply that it is possible.
>>
>> Maybe it's failing on something else? VM-entry instruction length? I
>> see that it must be in the range 1-15.
>>
>>
> It is VM instruction failure with error # 7, which means bad VM control.
> Also one difference for software interrupt is that HW will adjust guest
> IP automatically.
>
So you could set instruction length to 1 and adjust rip backwards by 1 :)
Though you may need to remember the adjustment and undo it if you get a
page fault on the IVT.
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-26 10:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 9:17 FW: [kvm-commits] KVM: Move interrupt injection out of interruptdisabled section Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A023EF364-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-17 15:42 ` Avi Kivity
[not found] ` <47162D74.6010408-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-18 1:10 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A023EF534-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-18 8:59 ` Avi Kivity
[not found] ` <47172084.7020608-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-18 10:16 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A023EF981-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-18 13:08 ` Avi Kivity
2007-10-26 8:27 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02482B8C-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-26 9:13 ` Avi Kivity
[not found] ` <4721AFCB.1000502-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-26 9:33 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02482BF7-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-26 9:53 ` Avi Kivity
[not found] ` <4721B917.3010302-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-26 10:11 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02482C1C-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-26 10:13 ` Avi Kivity [this message]
[not found] ` <4721BDE5.4030308-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-26 10:17 ` Dong, Eddie
[not found] ` <10EA09EFD8728347A513008B6B0DA77A02482C1D-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-10-26 10:22 ` 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=4721BDE5.4030308@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox