> > > > What the status of userspace for this thing? Are QEMU patches being > > > > posted and reviewed? > > > > > > I didn't see a notification that the patches were merged. Are they in > > > Linus' tree yet? Then I can post enablement to qemu-devel. > > > > I think you got it backward. I have no intention of merging them until I > > see a vague consensus on the userspace API, and a set of patches ready > > to be merged in QEMU. > > That's not how kvm apis are made. Actually I think it's always been like this, depending on what Marc meant for "ready to be merged in QEMU". It doesn't make sense to merge KVM APIs without having userspace patches at least posted as RFC to qemu-devel, and without having at least a positive response from the QEMU architecture maintainer. ARM does require a bit more care because there's no overlap between kernel and userspace maintainers, so perhaps that's the source of the confusion? Now, of course merging the patches in QEMU may take a month or two depending on the timing (because you have to wait for the patches to be merged into Linus's tree and for the KVM headers to be updated in QEMU---which is not going to happen during freeze of course). So of course the KVM patch thus can be committed even if QEMU is in freeze, as long as the QEMU architecture maintainer gives an overall green light. In fact a couple weeks from now would be the perfect time to post the patches to QEMU. Then you can get a review from Peter once he's back from vacation (beginning of December), the KVM patches can easily make it for the 4.10 merge window (end of December), and the userspace patches will hopefully be merged in QEMU 2.9 in January 2017. Thanks, Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
