From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MP1tW-0001kX-71
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 18:15:10 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MP1tR-0001jd-RF
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 18:15:09 -0400
Received: from [199.232.76.173] (port=43877 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MP1tR-0001ja-Jm
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 18:15:05 -0400
Received: from mx20.gnu.org ([199.232.41.8]:43241)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <paul@codesourcery.com>)
	id 1MP1tR-00049j-Fw
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 18:15:05 -0400
Received: from mail.codesourcery.com ([65.74.133.4])
	by mx20.gnu.org with esmtp (Exim 4.60)
	(envelope-from <paul@codesourcery.com>) id 1MP1tQ-000848-0f
	for qemu-devel@nongnu.org; Thu, 09 Jul 2009 18:15:04 -0400
From: Paul Brook <paul@codesourcery.com>
Date: Thu, 9 Jul 2009 23:14:52 +0100
References: <4A565B42.3050005@us.ibm.com>
In-Reply-To: <4A565B42.3050005@us.ibm.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200907092314.52961.paul@codesourcery.com>
Subject: [Qemu-devel] Re: Disabling kqemu by default at runtime for 0.11
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: Anthony Liguori <aliguori@us.ibm.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Thursday 09 July 2009, Anthony Liguori wrote:
> We've talked about this at length but I'd like to pull the trigger.  The
> user-visible change would be that -enable-kqemu would be required to
> explicitly request kqemu support instead of enabling it by default.
> kqemu would still be enabled by default at build time.
>
> Do you object to this Paul?

i have no objection to disabling kqemu by default *at runtime*. This would 
make it the same as kvm.

On principle I object to having code that is disabled by default at configure 
time. IMO that code should either be removed or fixed. If we were to disable 
kqemu at configure time for 0.11 then I would expect to remove the code from 
trunk shortly after 0.11 was released.

Paul