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 v2] KVM: VMX: Print VM-instruction error when it may be helpful
Date: Tue, 10 May 2022 16:27:37 +0000 [thread overview]
Message-ID: <YnqSecml2/Ooc0E/@google.com> (raw)
In-Reply-To: <20220508040233.931710-1-jmattson@google.com>
On Sat, May 07, 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>
> ---
> arch/x86/kvm/vmx/vmx.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index d58b763df855..a25da991da07 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -392,12 +392,14 @@ noinline void vmwrite_error(unsigned long field, unsigned long value)
>
> noinline void vmclear_error(struct vmcs *vmcs, u64 phys_addr)
> {
> - vmx_insn_failed("kvm: vmclear failed: %p/%llx\n", vmcs, phys_addr);
> + vmx_insn_failed("kvm: vmclear failed: %p/%llx err=%d\n",
I highly doubt it will ever matter, but arguably this should be %u, not %d.
> + vmcs, phys_addr, vmcs_read32(VM_INSTRUCTION_ERROR));
> }
>
> noinline void vmptrld_error(struct vmcs *vmcs, u64 phys_addr)
> {
> - vmx_insn_failed("kvm: vmptrld failed: %p/%llx\n", vmcs, phys_addr);
> + vmx_insn_failed("kvm: vmptrld failed: %p/%llx err=%d\n",
> + vmcs, phys_addr, vmcs_read32(VM_INSTRUCTION_ERROR));
> }
>
> noinline void invvpid_error(unsigned long ext, u16 vpid, gva_t gva)
> --
> 2.36.0.512.ge40c2bad7a-goog
>
next prev parent reply other threads:[~2022-05-10 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 4:02 [PATCH v2] KVM: VMX: Print VM-instruction error when it may be helpful Jim Mattson
2022-05-10 16:27 ` Sean Christopherson [this message]
2022-05-10 22:24 ` Jim Mattson
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=YnqSecml2/Ooc0E/@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox