I was able to get rid of some nanoseconds for a guest exit loop on s390. I did my best to not break other architectures but review and comments on the general approach is welcome. Downside is that the existing irq_save things will just work no matter what the callers have done, the new code must do the right thing in the callers. Is that approach acceptible? Does anybody else see some measurable difference for guest exits? Christian Borntraeger (2): KVM: Push down irq_save to architectures before kvm_guest_enter KVM: push down irq_save from kvm_guest_exit arch/powerpc/kvm/book3s_hv.c | 4 ++++ arch/powerpc/kvm/book3s_pr.c | 2 ++ arch/powerpc/kvm/booke.c | 4 ++-- arch/s390/kvm/kvm-s390.c | 6 ++++-- arch/x86/kvm/x86.c | 2 ++ include/linux/kvm_host.h | 18 ++++++++---------- 6 files changed, 22 insertions(+), 14 deletions(-) -- 2.3.0 -- To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
