From mboxrd@z Thu Jan  1 00:00:00 1970
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: ioemu/qemu
Date: Tue, 1 Apr 2008 19:47:57 +0100
Message-ID: <20080401184757.GD5030@implementation>
References: <E2BB8074E5500C42984D980D4BD78EF9022A7073@MFG-NYC-EXCH2.mfg.prv>
	<20080401152527.GH4637@implementation.nationalexpresswifi.train>
	<E2BB8074E5500C42984D980D4BD78EF9022A7074@MFG-NYC-EXCH2.mfg.prv>
	<20080401154852.GI4637@implementation.nationalexpresswifi.train>
	<E2BB8074E5500C42984D980D4BD78EF9022A7079@MFG-NYC-EXCH2.mfg.prv>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <E2BB8074E5500C42984D980D4BD78EF9022A7079@MFG-NYC-EXCH2.mfg.prv>
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: "Ross S. W. Walker" <rwalker@medallion.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Ross S. W. Walker, le Tue 01 Apr 2008 14:41:17 -0400, a écrit :
> I have always wondered why the xen developers decided to keep the qemu
> name for the domain device provider

The directory is actually called ioemu (but indeed the program is called
qemu-dm).  The fact that all functions are still named qemu_* is just to
make upstream tracking easier.

> after they have completely gutted
> and pratically rewritten the original code?

No. The device emulation is as close to upstream as possible (or at
least, it should be :) )

Samuel