From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Graf Subject: [PATCH 0/5] Nested SVM Interrupt Fixes Date: Fri, 18 Sep 2009 15:00:27 +0200 Message-ID: <1253278832-31803-1-git-send-email-agraf@suse.de> To: kvm@vger.kernel.org Return-path: Received: from cantor2.suse.de ([195.135.220.15]:49033 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750879AbZIRNA3 (ORCPT ); Fri, 18 Sep 2009 09:00:29 -0400 Received: from relay1.suse.de (relay-ext.suse.de [195.135.221.8]) by mx2.suse.de (Postfix) with ESMTP id 2E83D8672B for ; Fri, 18 Sep 2009 15:00:33 +0200 (CEST) Sender: kvm-owner@vger.kernel.org List-ID: Looking through the interrupt handling paths I stumbled across several inconsitencies in the interrupt handling paths. Using this patchset, running the most recent KVM version in nested KVM works again. Alexander Graf (5): Implement #NMI exiting for nested SVM Don't call svm_complete_interrupts for nested guests Don't #VMEXIT(INTR) if we still have event_inj waiting Don't bail when injecting an event in nested SVM Notify nested hypervisor of lost event injections arch/x86/kvm/svm.c | 79 ++++++++++++++++++++++++++++++++++++++++++++------- 1 files changed, 68 insertions(+), 11 deletions(-)