public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Guillaume Thouvenin <guillaume.thouvenin-Z51IpKcfGtLk1uMJSBkQmQ@public.gmane.org>
To: Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [ToDo] Real Mode Support
Date: Wed, 6 Feb 2008 13:07:19 +0100	[thread overview]
Message-ID: <20080206130719.3db4d68a@frecb000711> (raw)
In-Reply-To: <1202287974.23342.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>

On Wed, 06 Feb 2008 10:52:54 +0200
Izik Eidus <izike-atKUWr5tajBWk0Htik3J/w@public.gmane.org> wrote:
> 
> i am not expert for the emulator area, but as far as i remember:
> 
> virtual 8086 have some checks related to segments (the big mode
> problem), it mean that for some addresses it wont be able to execute
> anything, you will just get vmexit right away, therefor you need a full
> functional emulator that will handle everything there.

Oh thanks,  I remember now. The problem seems to be with the descriptor
cache register. In protected mode and also in virtual mode the
descriptor cache register is fully loaded each time a segment register
is loaded. It's not the case in real mode. So every program that uses
this "feature" (the big real mode) will not work under vm8086.
Thus we need to remove the usage of the virtual mode and instead we
need to fully emulate the real mode in order to be "big real mode"
compliant.

Does somebody know if there are already some patches or some other stuff
about big real mode support?
 
Regards,
Guillaume

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2008-02-06 12:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06  7:33 [ToDo] Real Mode Support Guillaume Thouvenin
2008-02-06  8:52 ` Izik Eidus
     [not found]   ` <1202287974.23342.8.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-02-06 12:07     ` Guillaume Thouvenin [this message]
2008-02-06 12:52       ` Izik Eidus
2008-02-06 23:52       ` Kamble, Nitin A
2008-02-07 18:36         ` Alexey Eremenko
2008-02-06 17:32 ` Anthony Liguori
     [not found]   ` <47A9EF21.3050103-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-02-06 17:47     ` Izik Eidus
2008-02-10 11:44   ` Avi Kivity
2008-02-11 13:39     ` Guillaume Thouvenin
2008-02-11 14:20       ` 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=20080206130719.3db4d68a@frecb000711 \
    --to=guillaume.thouvenin-z51ipkcfgtlk1umjsbkqmq@public.gmane.org \
    --cc=izike-atKUWr5tajBWk0Htik3J/w@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