From: Mingwei Zhang <mizhang@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Mingwei Zhang <mizhang@google.com>,
David Matlack <dmatlack@google.com>
Subject: [PATCH v4 0/3] Extend KVM trace_kvm_nested_vmrun() to support VMX
Date: Thu, 25 Aug 2022 22:57:52 +0000 [thread overview]
Message-ID: <20220825225755.907001-1-mizhang@google.com> (raw)
This patch set update trace_kvm_nested_vmrun() to support VMX. In
addition, add the guest_pgd field to enrich the trace information.
v3 -> v4:
- Rebase to tip of kvm/queue.
v2 -> v3:
- Split the insertion of guest pgd field into a separate patch [seanjc].
- Update field names as suggested [seanjc].
v2:
- https://lore.kernel.org/lkml/YurMLf3MDAK0RiZc@google.com/T/
v1 link:
- https://lore.kernel.org/lkml/20220708232304.1001099-2-mizhang@google.com/T/
David Matlack (1):
KVM: nVMX: Add tracepoint for nested vmenter
Mingwei Zhang (2):
KVM: x86: Update trace function for nested VM entry to support VMX
KVM: x86: Print guest pgd in kvm_nested_vmenter()
arch/x86/kvm/svm/nested.c | 8 ++++++--
arch/x86/kvm/trace.h | 33 +++++++++++++++++++++++----------
arch/x86/kvm/vmx/nested.c | 10 ++++++++++
arch/x86/kvm/x86.c | 2 +-
4 files changed, 40 insertions(+), 13 deletions(-)
base-commit: 372d07084593dc7a399bf9bee815711b1fb1bcf2
--
2.37.2.672.g94769d06f0-goog
next reply other threads:[~2022-08-25 22:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:57 Mingwei Zhang [this message]
2022-08-25 22:57 ` [PATCH v4 1/3] KVM: x86: Update trace function for nested VM entry " Mingwei Zhang
2022-08-30 20:31 ` Sean Christopherson
2022-08-25 22:57 ` [PATCH v4 2/3] KVM: nVMX: Add tracepoint for nested vmenter Mingwei Zhang
2022-08-25 22:57 ` [PATCH v4 3/3] KVM: x86: Print guest pgd in kvm_nested_vmenter() Mingwei Zhang
2022-08-30 21:29 ` Sean Christopherson
2022-08-30 20:29 ` [PATCH v4 0/3] Extend KVM trace_kvm_nested_vmrun() to support VMX Sean Christopherson
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=20220825225755.907001-1-mizhang@google.com \
--to=mizhang@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.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
all inboxes | Powered by JetHome®