From: Vitaly Kuznetsov Subject: Re: [PATCH RFC] KVM: x86: vmx: throttle immediate exit through preemtion timer to assist buggy guests Date: Mon, 01 Apr 2019 12:41:51 +0200 Message-ID: <87lg0u0zyo.fsf@vitty.brq.redhat.com> References: <20190328203110.20655-1-vkuznets@redhat.com> <87d0m93frp.fsf@vitty.brq.redhat.com> <89d4189b-de6a-7634-de8b-29a044a86e12@redhat.com> <63F1B6AE-F7A0-40D9-9582-558723800682@oracle.com> <32296de3-8ce0-c20a-5948-a7eef267a328@redhat.com> <87v9zy15mc.fsf@vitty.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Cc: Paolo Bonzini , kvm@vger.kernel.org, Radim =?utf-8?B?S3LEjW3DocWZ?= , Sean Christopherson , linux-kernel@vger.kernel.org To: Liran Alon Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Liran Alon writes: > So to sum-up: This matches what I mentioned in my previous emails right? > That vector 96 is not related, and the only issue here is that level-triggered interrupt handler for vector 80 is doing EOI before lowering the irq-line. > Which cause vector 80 to be injected in infinite loop. > And this is not even related to being a nested virtualization > workload. It’s just an issue in Hyper-V (L1) interrupt handler for > vector 80. Yes, it may be related to how communications between Hyper-V and Windows partition are organized but it's a pure speculation. > > Therefore the only action-items are: > 1) Microsoft to fix Hyper-V vector 80 interrupt handler to lower irq-line before EOI. > 2) Patch QEMU IOAPIC implementation to have a mechanism similar to KVM to delay injection of level-triggered interrupt > in case we are injecting the same interrupt for X times in a row. I'm intended to do 2) and we already let MS know there's an issue. Thanks for your help with the investigation guys! -- Vitaly