From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:38729) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ra9oe-0000si-94 for qemu-devel@nongnu.org; Mon, 12 Dec 2011 12:37:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ra9oa-0004jg-G6 for qemu-devel@nongnu.org; Mon, 12 Dec 2011 12:37:28 -0500 Received: from mx1.redhat.com ([209.132.183.28]:5469) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ra9oa-0004jS-9P for qemu-devel@nongnu.org; Mon, 12 Dec 2011 12:37:24 -0500 Message-ID: <4EE63BCA.9040204@redhat.com> Date: Mon, 12 Dec 2011 19:37:14 +0200 From: Avi Kivity MIME-Version: 1.0 References: <20111212163725.GA32142@amt.cnet> <4EE63123.101@siemens.com> In-Reply-To: <4EE63123.101@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v4 00/15] uq/master: Introduce basic irqchip support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Anthony Liguori , Lai Jiangshan , "kvm@vger.kernel.org" , "Michael S. Tsirkin" , Marcelo Tosatti , qemu-devel , Blue Swirl On 12/12/2011 06:51 PM, Jan Kiszka wrote: > > > > Any thoughts on the qemu-kvm merge plan? Sounds painful. > > Pain will be where the existing qemu-kvm extensions collide with these > refactored upstream devices (backend/frontend split specifically). > That's where we have to merge very carefully. Haven't tried this yet, > will give it a spin tomorrow or so. > > From that point on, disabling the new stuff for now and at some point > switching over from the old one should be simple again. > > BTW, PIT+HPET+speaker will cause similar issues for the same reasons. > It's a little late for this, but refactoring qemu-kvm in-tree and then splitting it into patches would have been easier. Let's try it this way for the next batch. -- error compiling committee.c: too many arguments to function