From: Mike Galbraith <efault@gmx.de>
To: Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: jmattson@google.com, wanpeng.li@hotmail.com
Subject: Re: [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection
Date: Fri, 28 Jul 2017 10:24:55 +0200 [thread overview]
Message-ID: <1501230295.9055.12.camel@gmx.de> (raw)
In-Reply-To: <20170728070310.4460-1-pbonzini@redhat.com>
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.
-Mike
next prev parent reply other threads:[~2017-07-28 8:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-28 7:03 [PATCH 0/2] KVM: nVMX: fixes to nested virt interrupt injection Paolo Bonzini
2017-07-28 7:03 ` [PATCH 1/2] KVM: nVMX: do not fill vm_exit_intr_error_code in prepare_vmcs12 Paolo Bonzini
2017-07-28 7:03 ` [PATCH 2/2] KVM: nVMX: fixes to nested virt interrupt injection Paolo Bonzini
2017-07-28 8:24 ` Mike Galbraith [this message]
2017-07-28 9:07 ` [PATCH 0/2] " Wanpeng Li
2017-07-28 11:53 ` Paolo Bonzini
2017-07-28 12:03 ` Mike Galbraith
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=1501230295.9055.12.camel@gmx.de \
--to=efault@gmx.de \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=wanpeng.li@hotmail.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