All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: x86: Print CPU of last attempted VM-entry when dumping VMCS/VMCB
Date: Tue, 22 Jun 2021 18:38:56 +0200	[thread overview]
Message-ID: <91dea6ce-4dbe-70cc-9c61-17d97f47d2e7@redhat.com> (raw)
In-Reply-To: <20210621221648.1833148-1-jmattson@google.com>

On 22/06/21 00:16, Jim Mattson wrote:
> Failed VM-entry is often due to a faulty core. To help identify bad
> cores, print the id of the last logical processor that attempted
> VM-entry whenever dumping a VMCS or VMCB.
> 
> Signed-off-by: Jim Mattson <jmattson@google.com>
> ---
>   arch/x86/kvm/svm/svm.c | 2 ++
>   arch/x86/kvm/vmx/vmx.c | 2 ++
>   2 files changed, 4 insertions(+)
> 
> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
> index 12c06ea28f5c..af9e9db1121e 100644
> --- a/arch/x86/kvm/svm/svm.c
> +++ b/arch/x86/kvm/svm/svm.c
> @@ -3132,6 +3132,8 @@ static void dump_vmcb(struct kvm_vcpu *vcpu)
>   		return;
>   	}
>   
> +	pr_err("VMCB %llx, last attempted VMRUN on CPU %d\n",
> +	       svm->current_vmcb->pa, vcpu->arch.last_vmentry_cpu);
>   	pr_err("VMCB Control Area:\n");
>   	pr_err("%-20s%04x\n", "cr_read:", control->intercepts[INTERCEPT_CR] & 0xffff);
>   	pr_err("%-20s%04x\n", "cr_write:", control->intercepts[INTERCEPT_CR] >> 16);
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index ab6f682645d7..94c7375eb75c 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -5724,6 +5724,8 @@ void dump_vmcs(struct kvm_vcpu *vcpu)
>   	if (cpu_has_secondary_exec_ctrls())
>   		secondary_exec_control = vmcs_read32(SECONDARY_VM_EXEC_CONTROL);
>   
> +	pr_err("VMCS %llx, last attempted VM-entry on CPU %d\n",
> +	       vmx->loaded_vmcs->vmcs, vcpu->arch.last_vmentry_cpu);
>   	pr_err("*** Guest State ***\n");
>   	pr_err("CR0: actual=0x%016lx, shadow=0x%016lx, gh_mask=%016lx\n",
>   	       vmcs_readl(GUEST_CR0), vmcs_readl(CR0_READ_SHADOW),
> 

Queued, thanks.

Paolo


      reply	other threads:[~2021-06-22 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 22:16 [PATCH] KVM: x86: Print CPU of last attempted VM-entry when dumping VMCS/VMCB Jim Mattson
2021-06-22 16:38 ` Paolo Bonzini [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=91dea6ce-4dbe-70cc-9c61-17d97f47d2e7@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jmattson@google.com \
    --cc=kvm@vger.kernel.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 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.