[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANRm+Cw5ss3m8WhVqQNiMd3wUfOAk_fG10NMACT60_LLnZMRrA@mail.gmail.com>
Date: Fri, 28 Jul 2017 17:07:20 +0800
From: Wanpeng Li <kernellwp@...il.com>
To: Mike Galbraith <efault@....de>
Cc: Paolo Bonzini <pbonzini@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kvm <kvm@...r.kernel.org>, Jim Mattson <jmattson@...gle.com>,
Wanpeng Li <wanpeng.li@...mail.com>
Subject: Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection
2017-07-28 16:24 GMT+08:00 Mike Galbraith <efault@....de>:
> 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.
Yeah, it is fixed in the kvm/queue.
https://git.kernel.org/pub/scm/virt/kvm/kvm.git/commit/?h=queue&id=1d518c6820daf4e00d29adfba980aee05f605f0f
Regards,
Wanpeng Li
Powered by blists - more mailing lists