From: Sean Christopherson <seanjc@google.com>
To: Jim Mattson <jmattson@google.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com,
David Matlack <dmatlack@google.com>
Subject: Re: [PATCH v3 1/2] KVM: VMX: Print VM-instruction error when it may be helpful
Date: Tue, 10 May 2022 23:50:41 +0000 [thread overview]
Message-ID: <Ynr6UeaXEYx58A+W@google.com> (raw)
In-Reply-To: <20220510224035.1792952-1-jmattson@google.com>
On Tue, May 10, 2022, Jim Mattson wrote:
> From: David Matlack <dmatlack@google.com>
>
> Include the value of the "VM-instruction error" field from the current
> VMCS (if any) in the error message for VMCLEAR and VMPTRLD, since each
> of these instructions may result in more than one VM-instruction
> error. Previously, this field was only reported for VMWRITE errors.
>
> Signed-off-by: David Matlack <dmatlack@google.com>
> [Rebased and refactored code; dropped the error number for INVVPID and
> INVEPT; reworded commit message.]
> Signed-off-by: Jim Mattson <jmattson@google.com>
> ---
I do think it'd be worthwhile to add the safe VMREAD variant, but I don't care
enough to hold this up.
Reviewed-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2022-05-10 23:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 22:40 [PATCH v3 1/2] KVM: VMX: Print VM-instruction error when it may be helpful Jim Mattson
2022-05-10 22:40 ` [PATCH v3 2/2] KVM: VMX: Print VM-instruction error as unsigned Jim Mattson
2022-05-10 23:51 ` Sean Christopherson
2022-05-17 20:21 ` Jim Mattson
2022-05-10 23:50 ` Sean Christopherson [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=Ynr6UeaXEYx58A+W@google.com \
--to=seanjc@google.com \
--cc=dmatlack@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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.