From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Byrne <john.l.byrne@hp.com>
Subject: Status of ioemu code in unstable?
Date: Mon, 18 Jul 2005 15:02:45 -0700
Message-ID: <42DC2705.6020206@hp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org


Hi,

I've been trying to find out from the xen-devel archives and Google and 
I cannot seem to find the information I'm looking for.

I assume the goal of the ioemu is to provide necessary support for 
non-paravirtualized guess running on VT-x hardware. At a minimum I'd 
guess you'd need BIOS emulation, display card emulation, and timer/ 
interrupt emulation.

I'd like to know what's there; what works; and what else might be 
needed. A pointer to the information or a summary would be appreciated. 
Also, there is one item in the todo list in the wiki that suggests that 
the ioemu code will all be re-written. Is this for performance reasons?

Thanks,

John Byrne