From: Anthony Liguori <anthony@codemonkey.ws>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm-devel@lists.sourceforge.net,
Guillaume Thouvenin <guillaume.thouvenin@ext.bull.net>,
Rik van Riel <riel@surriel.com>
Subject: Re: Real Mode Improvement on Intel Hosts - GSoC Project
Date: Thu, 24 Apr 2008 11:05:39 -0500 [thread overview]
Message-ID: <4810AFD3.4080901@codemonkey.ws> (raw)
In-Reply-To: <52d4a3890804240758q289a4809i1d607a93dc15ed24@mail.gmail.com>
Mohammed Gamal wrote:
> Hi,
> My Project proposal "Improving and Stabilizing Real-Mode Support for
> Intel Hosts" has been accepted into Google Summer of Code under the
> Linux Foundation. You may have a look at the proposal abstract here:
> http://code.google.com/soc/2008/linux/appinfo.html?csaid=1CC1C8B4CCC1120E
> .
>
> Any pointers on where to start, what would you like to see done, and
> any other comments and suggestions would greatly be appreciated.
>
We have a two stage plan to address real-mode on Intel systems. Both
involve using x86_emulate() to emulate 16-bit (and 32-bit) instructions
that VT cannot handle.
The first stage is to detect vmentry failures and run x86_emulate() for
a single instruction. If you look at the mailing list, you'll see
patches from myself and Guillaume. This should be enough to allow most
Ubuntu installer CDs to work under KVM. In this case, the CDs are using
a version of GFXBOOT that doesn't use big real mode, but still relies on
an undefined architectural aspect that VT doesn't support.
The second stage is to use a loop of x86_emulate() to run all 16-bit
code (instead of using vm86 mode). This will allow us to support guests
that use big real mode.
The best place to start is probably to try out some of the patches on
the list, and get familiar with the GFXBOOT assembly routines. There's
a #kvm in FreeNode, that's a good place to start if you're having
trouble getting started.
Regards,
Anthony Liguori
> Regards,
> Mohammed
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> kvm-devel mailing list
> kvm-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/kvm-devel
>
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-24 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 14:58 Real Mode Improvement on Intel Hosts - GSoC Project Mohammed Gamal
2008-04-24 15:47 ` Avi Kivity
2008-04-24 15:53 ` Mohammed Gamal
2008-04-24 16:05 ` Anthony Liguori [this message]
2008-04-25 6:05 ` Guillaume Thouvenin
2008-04-25 6:51 ` Avi Kivity
2008-04-25 7:27 ` Guillaume Thouvenin
2008-04-26 6:49 ` Avi Kivity
2008-04-26 9:29 ` Mohammed Gamal
2008-04-26 21:02 ` Avi Kivity
2008-04-26 15:19 ` Anthony Liguori
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=4810AFD3.4080901@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=guillaume.thouvenin@ext.bull.net \
--cc=kvm-devel@lists.sourceforge.net \
--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