From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:43859) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QzUmL-0003wW-TU for qemu-devel@nongnu.org; Fri, 02 Sep 2011 10:31:35 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QzUmK-0005RU-96 for qemu-devel@nongnu.org; Fri, 02 Sep 2011 10:31:33 -0400 Received: from mail-yi0-f45.google.com ([209.85.218.45]:56653) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QzUmK-0005RQ-6f for qemu-devel@nongnu.org; Fri, 02 Sep 2011 10:31:32 -0400 Received: by yih10 with SMTP id 10so2466446yih.4 for ; Fri, 02 Sep 2011 07:31:31 -0700 (PDT) Message-ID: <4E60E8C0.5040104@codemonkey.ws> Date: Fri, 02 Sep 2011 09:31:28 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <1314019498-8550-1-git-send-email-aliguori@us.ibm.com> <4E525B32.2010602@siemens.com> <4E5BD461.8040500@us.ibm.com> <850D6063-D602-4CB2-8834-BE6023D13F0E@web.de> <4E5BF571.9020607@codemonkey.ws> <18FA99D1-AC96-4EA3-8BCE-2BFDE84CF442@web.de> <4E5C03CC.3010707@codemonkey.ws> <4E5C15BB.5080000@web.de> <3345DE92-DEDA-4716-929D-8046E0EA2A00@web.de> <4E5D39D5.3000507@codemonkey.ws> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Qemu-devel] [PATCH] main: force enabling of I/O thread List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: Peter Maydell , Alexandre Raymond , qemu-devel Developers , Blue Swirl , Jan Kiszka , Paolo Bonzini , Alexander Graf , Aurelien Jarno On 09/01/2011 01:31 PM, Andreas Färber wrote: > Am 30.08.2011 um 21:28 schrieb Anthony Liguori: > >> On 08/30/2011 01:45 PM, Andreas Färber wrote: >>> Am 30.08.2011 um 00:42 schrieb Jan Kiszka: >>> >>>> What about making --enable-io-thread default as an intermediate step? >>>> That would leave --disable-io-thread as temporary workaround until all >>>> issues are fixed. The latter could generate a big fat warning that this >>>> mode will be removed before 1.0. >>> >>> Yes please, that proposal sounds much better. >>> >>> If http://wiki.qemu.org/Planning/1.0 is still up-to-date, we have about >>> six weeks to make I/O thread work everywhere. >> >> I'm not a big fan of just flipping the configure flag. There is other >> work being held up by disable-io-thread like the timer conversion. >> >> If there aren't known issues, then I want to remove the non-I/O thread >> code. git history is still there for anyone that wants to test w/o it. > > My problem is that at HEAD *none* of the i386,ppc,sparc guests that used > to work about a month ago boot *at all* on my Darwin/ppc64 host. > > Might be TCG, might be the new MemoryRegion API, might be (non-)I/O > thread. Means a lot of git history testing despite little time. An > ultimatum to make things even worse doesn't really help there... ;) For a platform to be supported, it needs to be actively maintained and fixed. If there aren't enough folks testing/fixing Darwin/ppc64, then it's not a platform we can reasonable support :-/ Regards, Anthony Liguori > > Andreas