From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LVYWX-0007Fc-Co for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:46:09 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LVYWV-0007DZ-3K for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:46:08 -0500 Received: from [199.232.76.173] (port=42192 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LVYWU-0007Cz-MM for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:46:06 -0500 Received: from mr01.hansenet.de ([213.191.74.10]:55437) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LVYWU-0002an-8D for qemu-devel@nongnu.org; Fri, 06 Feb 2009 16:46:06 -0500 Received: from exactcode.de (85.183.32.143) by mr01.hansenet.de (7.3.132) id 4967D2550030EBA2 for qemu-devel@nongnu.org; Fri, 6 Feb 2009 22:46:05 +0100 Received: from [82.113.106.17] (helo=[10.73.153.107]) by exactcode.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.54) id 1LVYWN-0003p3-Mg for qemu-devel@nongnu.org; Fri, 06 Feb 2009 21:46:04 +0000 Message-ID: <498CB13D.1080808@exactcode.com> Date: Fri, 06 Feb 2009 22:53:01 +0100 From: =?ISO-8859-1?Q?Ren=E9_Rebe?= MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: Cutting a new QEMU release References: <1233825194.6637.4.camel@ecrins.fosdick.home.net> <498AF6FC.90803@codemonkey.ws> <200902050936.49909.rickv@hobi.com> <200902051627.21972.paul@codesourcery.com> <498B380E.5090603@codemonkey.ws> <1233917676.6637.39.camel@ecrins.fosdick.home.net> <498C5DCC.3060106@exactcode.de> In-Reply-To: <498C5DCC.3060106@exactcode.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: Quoted-Printable Reply-To: 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 Ren=E9 Rebe wrote: > If I would know more of the internals of kqemu I would even volunteer t= o > maintain it - however, I just took the first look at it yesterday which= =20 > does > not really qualify to maintain it just yet. Though I would work on gett= ing > it adapted on future kernel changes, and/or even hunt a bug if it start= s > crashing in one or another scenario for me (but right now I have to hun= t > some crashing with 32bit host KVM for a start). Ok, those segfaults where due to an old non-NPTL glibc and the __thread support being nonfunctional in this combination used in the kvm tree :-) --=20 Ren=E9 Rebe - ExactCODE GmbH - Europe, Germany, Berlin http://exactcode.de | http://t2-project.org | http://rene.rebe.name