From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 2/5] KVM: x86: do not scan IRR twice on APICv vmentry Date: Thu, 3 Nov 2016 14:30:31 +0100 Message-ID: <00273a1a-ef5d-f814-3e02-24b4e855d229@redhat.com> References: <1476469291-5039-1-git-send-email-pbonzini@redhat.com> <1476469291-5039-3-git-send-email-pbonzini@redhat.com> <20161026195900.GC4212@potion> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, yang.zhang.wz@gmail.com, feng.wu@intel.com, mst@redhat.com To: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= Return-path: In-Reply-To: <20161026195900.GC4212@potion> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 26/10/2016 21:59, Radim Krčmář wrote: > 2016-10-14 20:21+0200, Paolo Bonzini: >> Calling apic_find_highest_irr results in IRR being scanned twice, >> once in vmx_sync_pir_from_irr and once in apic_search_irr. Change >> sync_pir_from_irr to do the RVI write and kvm_apic_update_irr to >> compute the new RVI on the fly. >> >> Signed-off-by: Paolo Bonzini >> --- > > Reviewed-by: Radim Krčmář Nope, this breaks nested VMX exit on external interrupt. For now I'm testing only patch 1 and will push that one only to kvm/next. Paolo