qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt


From: Avi Kivity
Subject: Re: [Qemu-devel] [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
Date: Mon, 21 May 2012 14:35:42 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]