From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Nadav Har'El" Subject: Re: [PATCH 25/31] nVMX: Correct handling of idt vectoring info Date: Wed, 25 May 2011 13:13:57 +0300 Message-ID: <20110525101357.GA14883@fermat.math.technion.ac.il> References: <1305575004-nyh@il.ibm.com> <201105161956.p4GJuikI002016@rice.haifa.ibm.com> <625BA99ED14B2D499DC4E29D8138F1505C9BFA3B11@shsmsx502.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "kvm@vger.kernel.org" , "gleb@redhat.com" , "avi@redhat.com" To: "Tian, Kevin" Return-path: Received: from mailgw12.technion.ac.il ([132.68.225.12]:16727 "EHLO mailgw12.technion.ac.il" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750783Ab1EYKOK (ORCPT ); Wed, 25 May 2011 06:14:10 -0400 Content-Disposition: inline In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1505C9BFA3B11@shsmsx502.ccr.corp.intel.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, May 25, 2011, Tian, Kevin wrote about "RE: [PATCH 25/31] nVMX: Correct handling of idt vectoring info": > Here got one question. How about L2 has interrupt exiting disabled? That way You are right, this is a bug in my code. It's a known bug - listed on my private bugzilla - but I didn't get around to fixing it. As I said, most hypervisors "in the wild" do not have interrupt exiting disabled, so this bug will not appear in practice, but definitely it should be fixed, and I will. When the nvmx patches are merged, I can can copy my private bug tracker's open issues to an open bug tracker (I'm hoping KVM has one?). Thanks, Nadav. -- Nadav Har'El | Wednesday, May 25 2011, 21 Iyyar 5771 nyh@math.technion.ac.il |----------------------------------------- Phone +972-523-790466, ICQ 13349191 |"I don't use drugs, my dreams are http://nadav.harel.org.il |frightening enough." -- M. C. Escher