[...] >>> + kvm_vcpu_on_spin(vcpu); >> >> Could you also enable CONFIG_HAVE_KVM_CPU_RELAX_INTERCEPT for arm and >> check if ple handler logic helps further? >> we would ideally get one more optimization folded into ple handler if >> you enable that. > > Just gave it a go, and the results are slightly (but consistently) > worse. Over 10 runs: > > Without RELAX_INTERCEPT: Average run 3.3623s > With RELAX_INTERCEPT: Average run 3.4226s > > Not massive, but still noticeable. Any clue? Is it a 4x overcommit? Probably we would have hit the code overhead if it were small guests. RELAX_INTERCEPT is worth enabling for large guests with overcommits. _______________________________________________ kvmarm mailing list kvmarm@xxxxxxxxxxxxxxxxxxxxx https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
