From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: Integrate kqemu emulation into xen hypervisor possible? Date: Tue, 1 Apr 2008 19:52:23 +0100 Message-ID: <20080401185223.GF31765@redhat.com> References: <20080401152527.GH4637@implementation.nationalexpresswifi.train> <20080401154852.GI4637@implementation.nationalexpresswifi.train> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Ross S. W. Walker" Cc: xen-devel@lists.xensource.com, Samuel Thibault List-Id: xen-devel@lists.xenproject.org On Tue, Apr 01, 2008 at 02:41:17PM -0400, Ross S. W. Walker wrote: > I have always wondered why the xen developers decided to keep the qemu > name for the domain device provider after they have completely gutted > and pratically rewritten the original code? Xen has not re-written the original code. QEMU provides both a CPU emulator and a plethora of devices. Xen merely uses the device emulation and not the CPU emulation. There's a few patches to integrate with Xen but it is not a re-write. > How about calling it just 'dm' for domain manager? No, renaming functional components for mere cosmetic reasons, will cause real world breakage for existing deployments. This is not a net win. Dan. -- |: Red Hat, Engineering, Boston -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|