From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1K3Czx-0003cc-BW
	for qemu-devel@nongnu.org; Mon, 02 Jun 2008 12:35:05 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1K3Czu-0003al-AF
	for qemu-devel@nongnu.org; Mon, 02 Jun 2008 12:35:04 -0400
Received: from [199.232.76.173] (port=45248 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1K3Czu-0003aZ-2E
	for qemu-devel@nongnu.org; Mon, 02 Jun 2008 12:35:02 -0400
Received: from mail2.shareable.org ([80.68.89.115]:57233)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1K3Czu-0007k0-7W
	for qemu-devel@nongnu.org; Mon, 02 Jun 2008 12:35:02 -0400
Received: from jamie by mail2.shareable.org with local (Exim 4.63)
	(envelope-from <jamie@shareable.org>) id 1K3Czr-0002Rs-AQ
	for qemu-devel@nongnu.org; Mon, 02 Jun 2008 17:34:59 +0100
Date: Mon, 2 Jun 2008 17:34:59 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Re: KQEMU code organization
Message-ID: <20080602163459.GE2679@shareable.org>
References: <483C3D55.2000508@siemens.com> <483C8705.307@bellard.org>
	<483D81FA.5070202@siemens.com> <483D8A2E.5070907@bellard.org>
	<483D8E9A.40509@siemens.com> <483EA1AD.1010901@bellard.org>
	<20080529161322.GB21610@shareable.org>
	<483ED935.2060802@codemonkey.ws> <483EDF80.3060003@siemens.com>
	<484125E3.1090003@qumranet.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <484125E3.1090003@qumranet.com>
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: qemu-devel@nongnu.org

Avi Kivity wrote:
> kvm started out with qemu emulating 16-bit code (and before that, even 
> 32-bit code; kvm only did 64-bit).
> 
> The reason I don't like this approach is that it makes the interface 
> complex and hard to understand, and makes kvm heavily tied into qemu.
> 
> Some problems that arise from having qemu emulate code:
> - difficult to do smp properly

Now that atomic ops will be translated to atomic ops, and futex is
translated to host futex, and I think this is solved.

> - qemu needs to be able to inject mmio for in-kernel emulated devices
> - in-kernel devices (lapic, etc.) need to interact with guest code 
> executing in userspace

These two seem to apply equally if kqemu is made to work with
in-kernel emulated devices, which seems useful for exactly the same
reasons as kvm does.

-- Jamie