Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
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. 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. 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. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
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 -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
On 05/17/2012 04:32 PM, Jan Kiszka wrote: [ changes in v2: rebase over uq/master ] This series is another major milestone of merging qemu-kvm into upstream. It implements the required interfaces and logic to directly inject MSI-X interrupts generated by the vhost-net kernel module into the KVM in-kernel irqchip. This involves - establishing MSI vector notifiers, so far triggered on relevant MSI-X configuration changes of subscribed PCI devices - support for static vIRQ-to-MSI routes - an API for linking an IRQFD with such a vIRQ - the usage of these services in virtio-pci to enable direct injection The series also contains some smaller refactorings of the KVM IRQ routing API such as automatic committing of route changes. It applies on top of the KVM MSI support series [1] posted recently. The complete stack is available at git://git.kiszka.org/qemu-kvm.git queues/kvm-msi-irqfd If the proposes API is acceptable, I will also provide some morphing patches for qemu-kvm to make the merge of both trees smoother. After this series, to only reasons to still use qemu-kvm for production purposes will be PCI device assignment and potential dependencies on legacy command line switches as well as vmstate formats (when requiring backward migration support). However, the majority of users should be able to switch to upstream QEMU seamlessly and finally receive the same level of performance on x86. Thanks, applied. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
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. -- MST -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFC][PATCH v2 00/11] uq/master: irqfd-based interrupt injection for virtio/vhost
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. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line unsubscribe kvm in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
