That result was only for patch 18 of the series, not pvspinlock in
general.
Okay - I've re-read the performance numbers and they are impressive, so no
objections from me.
The x86 impact seems to be a straightforward API change, with most of the
changes on the virtualization side. So:
Acked-by: Ingo Molnar <mingo@xxxxxxxxxx>
I guess you'd want to carry this in the KVM tree or so - maybe in a
separate branch because it changes Xen as well?
Thank you Ingo for taking a relook.
Gleb, Please let me know if you want me to resend the first 17 patches
with acked-bys. i.e excluding the 18th patch.
--
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
