From: "Radim Krčmář" <rkrcmar@redhat.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org, pfeiner@google.com
Subject: Re: [PATCH] kvm: nVMX: Fetch VM_INSTRUCTION_ERROR from vmcs02 on vmx->fail
Date: Thu, 29 Sep 2016 20:27:06 +0200 [thread overview]
Message-ID: <20160929182706.GB13257@potion> (raw)
In-Reply-To: <1473179601-19546-1-git-send-email-jmattson@google.com>
2016-09-06 09:33-0700, Jim Mattson:
> When forwarding a hardware VM-entry failure to L1, fetch the
> VM_INSTRUCTION_ERROR field from vmcs02 before loading vmcs01.
>
> (Note that there is an implicit assumption that the VM-entry failure was
> on the first VM-entry to vmcs02 after nested_vmx_run; otherwise, L1 is
> going to be very confused.)
>
> Signed-off-by: Jim Mattson <jmattson@google.com>
> Reviewed-by: Peter Feiner <pfeiner@google.com>
> ---
Applied to kvm/queue, thanks.
prev parent reply other threads:[~2016-09-29 18:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 16:33 [PATCH] kvm: nVMX: Fetch VM_INSTRUCTION_ERROR from vmcs02 on vmx->fail Jim Mattson
2016-09-29 18:27 ` Radim Krčmář [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=20160929182706.GB13257@potion \
--to=rkrcmar@redhat.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pfeiner@google.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