From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost Date: Mon, 21 May 2012 14:35:42 +0300 Message-ID: <4FBA288E.9000208@redhat.com> References: <20120520144227.GB17809@redhat.com> <4FB9039A.3090107@redhat.com> <4FBA2784.8010605@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , Marcelo Tosatti , kvm@vger.kernel.org, qemu-devel To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:4563 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751045Ab2EULfv (ORCPT ); Mon, 21 May 2012 07:35:51 -0400 In-Reply-To: <4FBA2784.8010605@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: 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