Excerpts from Paolo Bonzini's message of February 23, 2022 12:11 am: > On 2/22/22 07:47, Nicholas Piggin wrote: >> Patch 3 requires a KVM_CAP_PPC number allocated. QEMU maintainers are >> happy with it (link in changelog) just waiting on KVM upstreaming. Do >> you have objections to the series going to ppc/kvm tree first, or >> another option is you could take patch 3 alone first (it's relatively >> independent of the other 2) and ppc/kvm gets it from you? > > Hi Nick, > > I have pushed a topic branch kvm-cap-ppc-210 to kvm.git with just the > definition and documentation of the capability. ppc/kvm can apply your > patch based on it (and drop the relevant parts of patch 3). I'll send > it to Linus this week. Hey Paolo, Thanks for this, I could have done it for you! This seems like a good way to reserve/merge caps: when there is a series ready for N+1, then merge window then the cap number and description could have a topic branch based on an earlier release. I'm not sure if you'd been doing that before (looks like not for the most recent few caps, at least). One thing that might improve it is if you used 5.16 as the base for the kvm-cap branch. I realise it wasn't so simple this time because 5.17-rc2 had a new cap merged. But it should be possible if all new caps took this approach. It would give the arch tree more flexibility where to base their tree on without (mpe usually does -rc2). NBD just an idea for next time. Thanks, Nick
