From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1DgRAC-0002vh-AM
	for qemu-devel@nongnu.org; Thu, 09 Jun 2005 13:49:56 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1DgRA0-0002sk-5V
	for qemu-devel@nongnu.org; Thu, 09 Jun 2005 13:49:45 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1DgR9w-0002hX-Gs
	for qemu-devel@nongnu.org; Thu, 09 Jun 2005 13:49:40 -0400
Received: from [143.183.121.16] (helo=scsfmr004.sc.intel.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1DgQvo-0000g6-5S
	for qemu-devel@nongnu.org; Thu, 09 Jun 2005 13:35:04 -0400
Date: Thu, 9 Jun 2005 10:37:34 -0700
From: Arun Sharma <arun.sharma@intel.com>
Message-ID: <20050609173734.GA23989@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Subject: [Qemu-devel] Re: Intel VMX support?
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: nate@root.org
Cc: qemu-devel@nongnu.org

Nate Lawson wrote:
> Have you considered adding support for this instruction set?
> http://cache-www.intel.com/cd/00/00/19/76/197666_197666.pdf

It's not clear if you're trying to execute instructions such as VMREAD
inside qemu or use qemu's device models + VT-x (used to be called VMX)
for executing instructions.

If it's the latter, the code is in xen-unstable now. Can boot Linux,
FreeBSD, MSDOS etc.

We took a 0.6.1 snapshot and were able to run with very few modifications
to the "hw" directory.

There were some discussions on where qemu should run on xen-devel (Look
for the thread "Device model architecture")

The main changes we did were:

- accelerate i8254 by moving parts into the hypervisor
- We had some hacks to run without the BIOS, but now that we have BIOS
  support, these can go away.

In general, we do have a desire to keep the tools/ioemu/hw directory in
Xen insync with the upstream qemu development.

Comments/suggestions?

        -Arun