From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753887AbcFPIVq (ORCPT ); Thu, 16 Jun 2016 04:21:46 -0400 Received: from mail-wm0-f66.google.com ([74.125.82.66]:33759 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751563AbcFPIVm (ORCPT ); Thu, 16 Jun 2016 04:21:42 -0400 From: Paolo Bonzini To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org Cc: bsd@redhat.com, rkrcmar@redhat.com Subject: [RFC PATCH 0/2] KVM: x86: guest exit microoptimization Date: Thu, 16 Jun 2016 10:21:35 +0200 Message-Id: <1466065297-4644-1-git-send-email-pbonzini@redhat.com> X-Mailer: git-send-email 1.8.3.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org This saves about 20 clock cycles per vmexit by avoiding a local_irq_save/restore pair. The price is that nested VMX will break with KVM hosts < 3.16, because the "acknowledge interrupt on exit" feature becomes mandatory. What do you think? Paolo Paolo Bonzini (2): KVM: x86: always use "acknowledge interrupt on exit" KVM: x86: use __kvm_guest_exit arch/x86/kvm/svm.c | 6 ++++++ arch/x86/kvm/vmx.c | 11 ++++------- arch/x86/kvm/x86.c | 11 ++--------- 3 files changed, 12 insertions(+), 16 deletions(-) -- 1.8.3.1