From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mike Galbraith Subject: Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection Date: Fri, 28 Jul 2017 10:24:55 +0200 Message-ID: <1501230295.9055.12.camel@gmx.de> References: <20170728070310.4460-1-pbonzini@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Cc: jmattson@google.com, wanpeng.li@hotmail.com To: Paolo Bonzini , linux-kernel@vger.kernel.org, kvm@vger.kernel.org Return-path: In-Reply-To: <20170728070310.4460-1-pbonzini@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Fri, 2017-07-28 at 09:03 +0200, Paolo Bonzini wrote: > With these two patches, KVM does not blindly pass the exit interruption > info and exit qualification from the vmcs02 and vmcs12 when injecting > an exception. There were two spots where this was done, namely > nested_vmx_check_exception and vmx_inject_page_fault_nested. > > Patch 1 avoids writing the vmcs02's VM_EXIT_INTR_ERROR_CODE field, > which as Jim noticed isn't possible on pre-Haswell machines, but > otherwise has no semantic effect. > > Patch 2 is the actual bugfix. I was looking into oodles of lapic_timer.hv_timer_in_use warnings in RT, introduced by KVM: LAPIC: Fix lapic timer injection delay, when I noticed this post.  Happily, I can report that they are history. -Mike