From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=44536 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Pv4a3-0002ph-Iq for qemu-devel@nongnu.org; Thu, 03 Mar 2011 04:12:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Pv4a2-0005KG-OM for qemu-devel@nongnu.org; Thu, 03 Mar 2011 04:12:19 -0500 Received: from mx1.redhat.com ([209.132.183.28]:20519) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Pv4a2-0005K3-G2 for qemu-devel@nongnu.org; Thu, 03 Mar 2011 04:12:18 -0500 Message-ID: <4D6F5B66.1010004@redhat.com> Date: Thu, 03 Mar 2011 11:12:06 +0200 From: Avi Kivity MIME-Version: 1.0 References: <1298884224-19734-1-git-send-email-pbonzini@redhat.com> <4D6B67E0.4040408@redhat.com> <4D6B7479.5010307@redhat.com> <4D6B8D92.8050807@siemens.com> <4D6B9154.6000601@redhat.com> <4D6BAB8C.4040508@redhat.com> <4D6CE82C.3030702@redhat.com> <20110302184309.GA21289@amt.cnet> <4D6E948E.4050207@siemens.com> <20110302193634.GB22743@amt.cnet> <20110302194223.GA23050@amt.cnet> <4D6F55F2.7070205@redhat.com> <4D6F5A38.1040209@siemens.com> In-Reply-To: <4D6F5A38.1040209@siemens.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH v3 uq/master 00/22] Win32 iothread support List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: "kvm@vger.kernel.org" , Marcelo Tosatti , "qemu-devel@nongnu.org" , "blauwirbel@gmail.com" , Paolo Bonzini , "aurelien@aurel32.net" On 03/03/2011 11:07 AM, Jan Kiszka wrote: > > > > Well that's strange, since qemu-kvm now passes autotest (and this was > > qemu.git + patchset, not qemu-kvm). > > > > Does it fail every time? Have you tested if qemu.git also fails without > the patches? Then we may have a chance to bisect. I didn't check. For extended testing it's better if Paolo or you get their own autotest setup. I'm happy to run the occasional test for anyone but for digging in, it takes too much time and commits machine resources I need for other things. Setting up autotest can be daunting, but the autotest people are *very* helpful. I'm sure they'll be happy to hand-hold until you get things working. -- error compiling committee.c: too many arguments to function