public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Liran Alon <liran.alon@oracle.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Sean Christopherson" <sean.j.christopherson@intel.com>,
	linux-kernel@vger.kernel.org
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	[thread overview]
Message-ID: <87lg0u0zyo.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <B70317FC-A5AF-41B7-8D1E-A38B14806FE4@oracle.com>

Liran Alon <liran.alon@oracle.com> 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

  reply	other threads:[~2019-04-01 10:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 20:31 [PATCH RFC] KVM: x86: vmx: throttle immediate exit through preemtion timer to assist buggy guests Vitaly Kuznetsov
2019-03-29  2:00 ` Liran Alon
2019-03-29  9:14   ` Vitaly Kuznetsov
2019-03-29 12:09     ` Liran Alon
2019-03-29 14:18 ` Paolo Bonzini
2019-03-29 14:40   ` Vitaly Kuznetsov
2019-03-29 15:01     ` Paolo Bonzini
2019-03-29 15:14       ` Vitaly Kuznetsov
2019-03-29 15:32       ` Liran Alon
2019-03-29 17:14         ` Paolo Bonzini
2019-04-01  8:39           ` Vitaly Kuznetsov
2019-04-01 10:08             ` Liran Alon
2019-04-01 10:41               ` Vitaly Kuznetsov [this message]
2019-04-01  8:50       ` Vitaly Kuznetsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87lg0u0zyo.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liran.alon@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox