From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:52563) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qy9Kr-00078Z-1V for qemu-devel@nongnu.org; Mon, 29 Aug 2011 17:25:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qy9Kp-0004Mc-TG for qemu-devel@nongnu.org; Mon, 29 Aug 2011 17:25:36 -0400 Received: from mail-yw0-f45.google.com ([209.85.213.45]:46807) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qy9Kp-0004MS-Qn for qemu-devel@nongnu.org; Mon, 29 Aug 2011 17:25:35 -0400 Received: by ywf9 with SMTP id 9so5791862ywf.4 for ; Mon, 29 Aug 2011 14:25:35 -0700 (PDT) Message-ID: <4E5C03CC.3010707@codemonkey.ws> Date: Mon, 29 Aug 2011 16:25:32 -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> In-Reply-To: <18FA99D1-AC96-4EA3-8BCE-2BFDE84CF442@web.de> 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 , Jan Kiszka , qemu-devel Developers , Blue Swirl , Paolo Bonzini , Alexander Graf , Aurelien Jarno On 08/29/2011 04:23 PM, Andreas Färber wrote: > Am 29.08.2011 um 22:24 schrieb Anthony Liguori: > >> On 08/29/2011 03:21 PM, Andreas Färber wrote: >>> Am 29.08.2011 um 20:03 schrieb Anthony Liguori: >>> >>>> On 08/22/2011 08:35 AM, Jan Kiszka wrote: >>>>> On 2011-08-22 15:24, Anthony Liguori wrote: >>>>>> Enabling the I/O thread by default seems like an important part of >>>>>> declaring >>>>>> 1.0. >>>> >>>> Given that [1] has been applied now, is there any objections to this >>>> patch? >>> >>> There had been additional patches to fix I/O thread issues on Darwin, >>> have any such fixes been applied the last few weeks? >> >> I don't see any outstanding Darwin patches in my queue so either they >> were applied or there were issues with them. > > Alexandre recalled his series on July 25, I spot neither explanation of > what was wrong with it nor a v2. Hope he'll explain. If there's uncertainty, I'd prefer to enable it sooner than later. This is a key 1.0 feature IMHO and I'd prefer to have more time to work through any issues. Regards, Anthony Liguroi > Andreas