From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LV8OK-0001Br-Qv for qemu-devel@nongnu.org; Thu, 05 Feb 2009 12:51:56 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LV8OI-00019t-8w for qemu-devel@nongnu.org; Thu, 05 Feb 2009 12:51:56 -0500 Received: from [199.232.76.173] (port=38128 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LV8OI-00019j-0k for qemu-devel@nongnu.org; Thu, 05 Feb 2009 12:51:54 -0500 Received: from mx1.redhat.com ([66.187.233.31]:51928) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LV8OH-00006W-Gd for qemu-devel@nongnu.org; Thu, 05 Feb 2009 12:51:53 -0500 Date: Thu, 5 Feb 2009 17:51:16 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] Re: Cutting a new QEMU release Message-ID: <20090205175116.GC2759@redhat.com> References: <1233825194.6637.4.camel@ecrins.fosdick.home.net> <200902051627.21972.paul@codesourcery.com> <498B1EC6.8000504@exactcode.de> <200902051736.23247.paul@codesourcery.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200902051736.23247.paul@codesourcery.com> Reply-To: "Daniel P. Berrange" , qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: =?utf-8?B?UmVuw6k=?= Rebe On Thu, Feb 05, 2009 at 05:36:22PM +0000, Paul Brook wrote: > > given the sheer amount of CPU sililcon without VT/SVM it looks to be worth > > keeping [kqemu] working. Maybe just to pull it into the Qemu SVN? > > I'd rather not. What you[1] really need to do is get it merged into upstream > linux kernels. There have been several threads about this previously, the > short version is that it probably involves rewriting to use the kvm API. > You'll find that many developers (including myself) have extremely low > tolerance for out of tree kernel modules[2]. More fundamentally, whether in or out of tree, someone needs to step forward & commit to being an active long term maintainer for the code. Having it in QEMU SVN without someone maintaining it won't help the current situation, and nor will dumping it upstream without someone maintaining it. Regards, Daniel -- |: Red Hat, Engineering, London -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 :|