From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dongxiao Xu Subject: [PATCH] nvmx: fix unhandled nested XSETBV VMExit Date: Wed, 29 Aug 2012 11:43:59 +0800 Message-ID: <1346211839-32707-1-git-send-email-dongxiao.xu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org If the L2 guest issue a XSETBV instruction, we need to deliver to L1 guest. This could fix the Fedora 17 booting hang issue as a L2 guest. Signed-off-by: Dongxiao Xu --- xen/arch/x86/hvm/vmx/vvmx.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/xen/arch/x86/hvm/vmx/vvmx.c b/xen/arch/x86/hvm/vmx/vvmx.c index 5f6553d..73ccf63 100644 --- a/xen/arch/x86/hvm/vmx/vvmx.c +++ b/xen/arch/x86/hvm/vmx/vvmx.c @@ -1506,6 +1506,7 @@ int nvmx_n2_vmexit_handler(struct cpu_user_regs *regs, case EXIT_REASON_VMXOFF: case EXIT_REASON_VMXON: case EXIT_REASON_INVEPT: + case EXIT_REASON_XSETBV: /* inject to L1 */ nvcpu->nv_vmexit_pending = 1; break; -- 1.7.1