From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MbZC0-00007f-Nt for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:14:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MbZBv-00005A-R9 for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:14:04 -0400 Received: from [199.232.76.173] (port=49628 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MbZBv-00004w-LP for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:13:59 -0400 Received: from mx20.gnu.org ([199.232.41.8]:31728) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MbZBv-0008La-GM for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:13:59 -0400 Received: from mail.codesourcery.com ([65.74.133.4]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MbZBu-0005ES-3O for qemu-devel@nongnu.org; Thu, 13 Aug 2009 08:13:58 -0400 From: Paul Brook Subject: Re: [Qemu-devel] [PATCH 1/2] Unbreak large mem support by removing kqemu Date: Thu, 13 Aug 2009 13:13:47 +0100 References: <1249942586-12671-1-git-send-email-aliguori@us.ibm.com> In-Reply-To: <1249942586-12671-1-git-send-email-aliguori@us.ibm.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200908131313.47711.paul@codesourcery.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Anthony Liguori > kqemu introduces a number of restrictions on the i386 target. > kvm is a viable alternative for people looking to accelerate qemu and has > the benefit of being supported by the upstream Linux kernel. If someone > can implement work arounds to remove the restrictions introduced by kqemu, > I'm happy to avoid and/or revert this patch. > Paul, please Ack or Nack this patch. Ok. I think we've kept kqemu lying around in a semi-broken state long enough that we can demonstrate lack of active developer interest. Anyone that really cares can always retrieve it from git history and start from there. Paul