From: Sean Christopherson <sean.j.christopherson@intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/2] KVM: nVMX: add tracepoints for nested VM-Enter failures
Date: Tue, 27 Aug 2019 15:27:14 -0700 [thread overview]
Message-ID: <20190827222714.GL27459@linux.intel.com> (raw)
In-Reply-To: <20190711155830.15178-1-sean.j.christopherson@intel.com>
Ping.
On Thu, Jul 11, 2019 at 08:58:28AM -0700, Sean Christopherson wrote:
> Debugging VM-Enter failures has been the bane of my existence for years.
> Seeing KVM's VMCS dump format pop up on a console triggers a Pavlovian
> response of swear words and sighs. As KVM's coverage of VM-Enter checks
> improve, so too do the odds of being able to triage/debug a KVM (or any
> other hypervisor) bug by running the bad KVM build as an L1 guest.
>
> Improve support for using KVM to debug a buggy VMM by adding tracepoints
> to capture the basic gist of a VM-Enter failure so that extracting said
> information from KVM doesn't require attaching a debugger or modifying
> L0 KVM to manually log failures.
>
> The captured information is by no means complete or perfect, e.g. I'd
> love to capture *exactly* why a consistency check failed, but logging
> that level of detail would require invasive code changes and might even
> act as a deterrent to adding more checks in KVM.
>
> v3: Fix a minor snafu in the v2 rebase, and re-rebase to kvm/next
> (a45ff5994c9c, "Merge tag 'kvm-arm-for-5.3'...")
>
> v2: Rebase to kvm/queue.
>
> Sean Christopherson (2):
> KVM: nVMX: add tracepoint for failed nested VM-Enter
> KVM: nVMX: trace nested VM-Enter failures detected by H/W
>
> arch/x86/include/asm/vmx.h | 14 ++
> arch/x86/kvm/trace.h | 22 +++
> arch/x86/kvm/vmx/nested.c | 269 ++++++++++++++++++++-----------------
> arch/x86/kvm/x86.c | 1 +
> 4 files changed, 179 insertions(+), 127 deletions(-)
>
> --
> 2.22.0
>
next prev parent reply other threads:[~2019-08-27 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 15:58 [PATCH v3 0/2] KVM: nVMX: add tracepoints for nested VM-Enter failures Sean Christopherson
2019-07-11 15:58 ` [PATCH v3 1/2] KVM: nVMX: add tracepoint for failed nested VM-Enter Sean Christopherson
2019-07-11 15:58 ` [PATCH v3 2/2] KVM: nVMX: trace nested VM-Enter failures detected by H/W Sean Christopherson
2019-08-27 22:27 ` Sean Christopherson [this message]
2019-09-11 15:34 ` [PATCH v3 0/2] KVM: nVMX: add tracepoints for nested VM-Enter failures 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=20190827222714.GL27459@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@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;
as well as URLs for NNTP newsgroup(s).