From: Mohammed Gamal <m.gamal005@gmail.com>
To: kvm@vger.kernel.org
Cc: avi@qumranet.com, riel@surriel.com, laurent.vivier@bull.net,
guillaume.thouvenin@ext.bull.net
Subject: [PATCH 0/4] VMX: Invalid guest state emulation
Date: Sun, 17 Aug 2008 16:36:15 +0300 [thread overview]
Message-ID: <20080817133615.GA8743@mohd-laptop> (raw)
The patch series adds invalid guest state emulation for VMX hosts, which is needed in order to properly support real mode guests.
Usually, a guest would be in an VMX-invalid state during mode switches from real to protected mode or vice versa.
We handle this invalid state by using the x86 emulator to emulate instructions until we arrive back to a VMX-friendly state.
This is achieved by:
- Adding thorough guest state checking in order to catch and handle invalid states
- Adding a guest state handler which emulates instructions till guest state is valid
- Adding an "emulation required" flag, enabled on mode switches, to indicated that emulation is needed
- Checking for guest state on vcpu_run() and emulating instructions instead of entering VMX if the state is invalid.
The next step needed is to add more instructions to the x86 emulator, since we might run into instructions not supported yet.
In order not to interfere with normal KVM operation, a module parameter 'emulate_invalid_guest_state' -which is disabled by default- that is used in
order to drive emulation. Bear in mind that currently you can't use this patch alone to get real mode guests to work. There is still a lot of work
needed on the x86 emulator in order not to run into failures running these guests.
next reply other threads:[~2008-08-17 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 13:36 Mohammed Gamal [this message]
2008-08-18 10:15 ` [PATCH 0/4] VMX: Invalid guest state emulation 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=20080817133615.GA8743@mohd-laptop \
--to=m.gamal005@gmail.com \
--cc=avi@qumranet.com \
--cc=guillaume.thouvenin@ext.bull.net \
--cc=kvm@vger.kernel.org \
--cc=laurent.vivier@bull.net \
--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