WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] VMX support for MMIO/PIO in VM8086 mode

To: Leendert van Doorn <leendert@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] VMX support for MMIO/PIO in VM8086 mode
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sat, 2 Apr 2005 08:25:51 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 02 Apr 2005 07:31:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050402064934.297AE106B@xxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20050402064934.297AE106B@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 2 Apr 2005, at 07:49, Leendert van Doorn wrote:

Memory mapped and port I/O is currently broken under VMX when the
partition is running in VM8086 mode. The reason is that the instruction
decoding support uses 32-bit opcode/address decodes rather 16-bit
decodes. This patch fixes that. In addition, the patch adds support for
the "stos" instruction decoding because this is a frequently used way
to clear MMIO areas such as the screen.

As an aside, vmx_platform.c should really reuse x86_emulate.c as much
as possible.

The memory-fault emulator needs proper support for 16-bit addressing and vm86 mode, which won't be hard to hard. I also need to pull the privileged-op emulator out of traps.c, and abstract out the action parts of it (e.g., actual move to/from CR, move to/from I/O port) in the same way I abstracted memory accesses in the mem-fault emulator.

There's less of a win in sharing the priv-op emulator since it is so much simpler, but it should still clean up the code a bunch.

 -- Keir


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>