From: Maran Wilson <maran.wilson@oracle.com>
To: Liran Alon <liran.alon@oracle.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, Joao Martins <joao.m.martins@oracle.com>,
ehabkost@redhat.com, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 3/4] target/i386: kvm: Save nested-state only in case vCPU have set VMXON region
Date: Tue, 9 Jul 2019 10:21:32 -0700 [thread overview]
Message-ID: <f264c433-facc-5316-e3e7-11a7bb97ea7a@oracle.com> (raw)
In-Reply-To: <20190705210636.3095-4-liran.alon@oracle.com>
On 7/5/2019 2:06 PM, Liran Alon wrote:
> Having (nested_state->hdr.vmx.vmxon_pa != -1ull) signals that vCPU have set
> at some point in time a VMXON region. Note that even though when vCPU enters
> SMM mode it temporarily exit VMX operation, KVM still reports (vmxon_pa != -1ull).
> Therefore, this field can be used as a reliable indicator on when we require to
s/on when we require/for when we are required/
Also, note that you have commit message lines are longer than 76
characters (longer than 80, for that matter).
But aside from those nits:
Reviewed-by: Maran Wilson <maran.wilson@oracle.com>
Thanks,
-Maran
> send VMX nested-state as part of migration stream.
>
> Reviewed-by: Joao Martins <joao.m.martins@oracle.com>
> Signed-off-by: Liran Alon <liran.alon@oracle.com>
> ---
> target/i386/machine.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/target/i386/machine.c b/target/i386/machine.c
> index 851b249d1a39..20bda9f80154 100644
> --- a/target/i386/machine.c
> +++ b/target/i386/machine.c
> @@ -997,9 +997,8 @@ static bool vmx_nested_state_needed(void *opaque)
> {
> struct kvm_nested_state *nested_state = opaque;
>
> - return ((nested_state->format == KVM_STATE_NESTED_FORMAT_VMX) &&
> - ((nested_state->hdr.vmx.vmxon_pa != -1ull) ||
> - (nested_state->hdr.vmx.smm.flags & KVM_STATE_NESTED_SMM_VMXON)));
> + return (nested_state->format == KVM_STATE_NESTED_FORMAT_VMX) &&
> + (nested_state->hdr.vmx.vmxon_pa != -1ull);
> }
>
> static const VMStateDescription vmstate_vmx_nested_state = {
next prev parent reply other threads:[~2019-07-09 17:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-05 21:06 [Qemu-devel] [PATCH 0/4] target/i386: kvm: Various nested-state fixes Liran Alon
2019-07-05 21:06 ` [Qemu-devel] [PATCH 1/4] target/i386: kvm: Init nested-state for VMX when vCPU expose VMX Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-11 13:45 ` Paolo Bonzini
2019-07-11 14:36 ` Liran Alon
2019-07-11 17:27 ` Paolo Bonzini
2019-07-05 21:06 ` [Qemu-devel] [PATCH 2/4] target/i386: kvm: Init nested-state for vCPU exposed with SVM Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-11 13:35 ` Paolo Bonzini
2019-07-05 21:06 ` [Qemu-devel] [PATCH 3/4] target/i386: kvm: Save nested-state only in case vCPU have set VMXON region Liran Alon
2019-07-09 17:21 ` Maran Wilson [this message]
2019-07-05 21:06 ` [Qemu-devel] [PATCH 4/4] target/i386: kvm: Demand nested migration kernel capabilities only when vCPU may have enabled VMX Liran Alon
2019-07-09 17:21 ` Maran Wilson
2019-07-15 9:20 ` Liran Alon
2019-07-15 9:25 ` Paolo Bonzini
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=f264c433-facc-5316-e3e7-11a7bb97ea7a@oracle.com \
--to=maran.wilson@oracle.com \
--cc=ehabkost@redhat.com \
--cc=joao.m.martins@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).