From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
"Liran Alon" <liran.alon@oracle.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 10:50:57 +0200 [thread overview]
Message-ID: <87sgv2153i.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <89d4189b-de6a-7634-de8b-29a044a86e12@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
>
> IIRC there was an enlightenment to tell Windows "I support auto-EOI but
> please don't use it". If this is what's happening, that would also fix it.
>
Unfortunately this doesn't save the day, Hyper-V behaves the
same. I'm more and move convinced that the secord IRQ was completely
unrelated:
[011] 515003.517644: kvm_exit: reason EPT_MISCONFIG rip 0xfffff80ca6bf1a5e info 0 0
[011] 515003.517645: kvm_nested_vmexit: rip fffff80ca6bf1a5e reason EPT_MISCONFIG info1 0 info2 0 int_info 0 int_info_err 0
[011] 515003.517649: kvm_emulate_insn: 0:fffff80ca6bf1a5e: 8b 08
[011] 515003.517652: vcpu_match_mmio: gva 0xffffd300eb0a8008 gpa 0x91044008 Read GPA
[011] 515003.517653: kvm_mmio: mmio unsatisfied-read len 4 gpa 0x91044008 val 0x0
[011] 515003.517654: kvm_fpu: unload
[011] 515003.517655: kvm_userspace_exit: reason KVM_EXIT_MMIO (6)
-> injecting
[007] 515003.517664: kvm_set_irq: gsi 23 level 1 source 0
[007] 515003.517666: kvm_msi_set_irq: dst 0 vec 80 (Fixed|physical|level)
[007] 515003.517667: kvm_apic_accept_irq: apicid 0 vec 80 (Fixed|edge)
[011] 515003.517688: kvm_fpu: load
[011] 515003.517689: kvm_mmio: mmio read len 4 gpa 0x91044008 val 0x1
[011] 515003.517692: kvm_nested_vmexit_inject: reason EXTERNAL_INTERRUPT info1 0 info2 0 int_info 80000050 int_info_err 0
[011] 515003.517696: kvm_entry: vcpu 0
-> immediate EOI
[011] 515003.517702: kvm_exit: reason EOI_INDUCED rip 0xfffff80002427e1a info 50 0
[011] 515003.517703: kvm_eoi: apicid 0 vector 80
[011] 515003.517704: kvm_fpu: unload
[011] 515003.517705: kvm_userspace_exit: reason KVM_EXIT_IOAPIC_EOI (26)
[011] 515003.517710: kvm_set_irq: gsi 23 level 1 source 0
[011] 515003.517711: kvm_msi_set_irq: dst 0 vec 80 (Fixed|physical|level)
[011] 515003.517712: kvm_apic_accept_irq: apicid 0 vec 80 (Fixed|edge)
[011] 515003.517714: kvm_fpu: load
[011] 515003.517716: kvm_entry: vcpu 0
[011] 515003.517720: kvm_exit: reason VMRESUME rip 0xfffff80002450115 info 0 0
[011] 515003.517726: kvm_entry: vcpu 0
[011] 515003.517729: kvm_exit: reason PREEMPTION_TIMER rip 0xfffff80ca6bf1a60 info 0 0
[011] 515003.517730: kvm_nested_vmexit: rip fffff80ca6bf1a60 reason PREEMPTION_TIMER info1 0 info2 0 int_info 0 int_info_err 0
[011] 515003.517732: kvm_nested_vmexit_inject: reason EXTERNAL_INTERRUPT info1 0 info2 0 int_info 80000050 int_info_err 0
[011] 515003.517735: kvm_entry: vcpu 0
[011] 515003.517739: kvm_exit: reason EOI_INDUCED rip 0xfffff80002427e1a info 50 0
[011] 515003.517739: kvm_eoi: apicid 0 vector 80
[011] 515003.517740: kvm_fpu: unload
[011] 515003.517741: kvm_userspace_exit: reason KVM_EXIT_IOAPIC_EOI (26)
[011] 515003.517743: kvm_set_irq: gsi 23 level 1 source 0
[011] 515003.517744: kvm_msi_set_irq: dst 0 vec 80 (Fixed|physical|level)
[011] 515003.517744: kvm_apic_accept_irq: apicid 0 vec 80 (Fixed|edge)
[011] 515003.517746: kvm_fpu: load
[011] 515003.517747: kvm_entry: vcpu 0
[011] 515003.517751: kvm_exit: reason VMRESUME rip 0xfffff80002450115 info 0 0
...
--
Vitaly
prev parent reply other threads:[~2019-04-01 8:50 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
2019-04-01 8:50 ` Vitaly Kuznetsov [this message]
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=87sgv2153i.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.