Am 23.02.22 um 12:47 schrieb Nicholas Piggin:
Excerpts from Christian Borntraeger's message of February 23, 2022 7:14 pm:
Am 22.02.22 um 15:11 schrieb Paolo Bonzini:
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.
We to have be careful with the 210 cap that was merged from the s390 tree.
Ah thanks, I didn't notice it.
Using 211 is no problem for me, merge will have a conflict now though.
We could avoid it by just sending my patch in a second batch instead of
doing the topic branch this time (I still like the idea of a topic
branch for caps for future).
Paolo,
the power people have not used your branch yet. So you could - as an alternative also
create an kvm-cap-ppc-211 branch for 5.17 and leave the s390 cap at 210. But it would
be good to do something now so that we have final numbers for the caps. Either create
a kvm-cap-ppc-211 branch, or merge the kvm-cap-ppc-210 branch into next and fixup the
s390 cap to become 211.
