From: Avi Kivity <avi@qumranet.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm@vger.kernel.org, riel@surriel.com
Subject: Re: [PATCH][RESEND] x86_emulator: Emulate cld and std instruction
Date: Thu, 31 Jul 2008 13:50:52 +0300 [thread overview]
Message-ID: <4891990C.7000202@qumranet.com> (raw)
In-Reply-To: <52d4a3890807310325r208b7943h89df5490e2af0131@mail.gmail.com>
Mohammed Gamal wrote:
> On Thu, Jul 31, 2008 at 12:57 PM, Avi Kivity <avi@qumranet.com> wrote:
>
>> Mohammed Gamal wrote:
>>
>>> This patch adds 'cld' and 'std' instructions to the emulator
>>>
>>>
>>>
>> I presume for big real mode? Which guest wants it?
>>
>
> Actually I was experimenting with checking guest state and emulating
> on mode switches. When I was doing so, it used to happen with all
> guests, so I guess it maybe something related to the BIOS not a
> specific guest.
>
There is indeed a cld in rombios.c (after rombios32_05), but it appears
to be after all segments have been initialized.
> BTW, the other way we can do is still handle vmentry failures. I
> discovered that the problem that caused occasional exits with
> Guillaume's patches is very likely to be that not enough checks on the
> guest state.
>
> The only check was if CS RPL equals SS RPL, so what happens is that
> when a vmexit and then a vmentry occurs CS and SS RPL maybe equal, but
> other checks might cause a vmentry failure. I've written a function to
> check that guest state is VMX valid - although not all checks are
> implemented yet, and I no more get the occasional vmexits.
>
I'm still worried about undoing the interrupt injection setup.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-31 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 21:27 [PATCH][RESEND] x86_emulator: Emulate cld and std instruction Mohammed Gamal
2008-07-31 9:57 ` Avi Kivity
2008-07-31 10:25 ` Mohammed Gamal
2008-07-31 10:50 ` Avi Kivity [this message]
2008-07-31 13:27 ` Mohammed Gamal
2008-07-31 18:16 ` Andrea Arcangeli
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=4891990C.7000202@qumranet.com \
--to=avi@qumranet.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=riel@surriel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox