From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:57152) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWQu6-0008Oo-Vd for qemu-devel@nongnu.org; Mon, 21 May 2012 07:36:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SWQtx-0001Lp-0i for qemu-devel@nongnu.org; Mon, 21 May 2012 07:35:58 -0400 Received: from mx1.redhat.com ([209.132.183.28]:9135) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SWQtw-0001LZ-Mi for qemu-devel@nongnu.org; Mon, 21 May 2012 07:35:48 -0400 Message-ID: <4FBA288E.9000208@redhat.com> Date: Mon, 21 May 2012 14:35:42 +0300 From: Avi Kivity MIME-Version: 1.0 References: <20120520144227.GB17809@redhat.com> <4FB9039A.3090107@redhat.com> <4FBA2784.8010605@siemens.com> In-Reply-To: <4FBA2784.8010605@siemens.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Marcelo Tosatti , qemu-devel , kvm@vger.kernel.org, "Michael S. Tsirkin" On 05/21/2012 02:31 PM, Jan Kiszka wrote: > On 2012-05-20 11:45, Avi Kivity wrote: > > On 05/20/2012 05:42 PM, Michael S. Tsirkin wrote: > >> On Thu, May 17, 2012 at 10:32:28AM -0300, Jan Kiszka wrote: > >>> After this series, to only reasons to still use qemu-kvm for production > >>> purposes will be PCI device assignment > >> > >> Yay! > >> > >> By the way, there are probably not many reasons to keep the > >> assignment code out of qemu.git. It duplicates a ton of > >> code from core pci, but that's easier to fix in-tree > >> than out of tree. > > > > Right. And Jan, if you want to push device assignment to qemu.git, > > please update it in qemu-kvm.git instead of rewriting it in qemu.git. > > > > That's precisely my plan. The conversion of pci-assign to the new APIs > is too hairy to combine it with a refactoring and upstream push. But > this depends on this series being merged back into qemu-kvm first. I'll try to expedite this. > This and also the previous MSI work will cause some merge conflicts. > Once upsteam accepted these series, I will provide the usual merge work > as pull request. Thanks in advance. > There are also some other "smaller" pieces to prepare for device > assignment (e.g. PCI IRQ routing hooks, full PCI address properties) > that I'm preparing for upstream. Will send some of them later. Okay - looking forward to that. -- error compiling committee.c: too many arguments to function