From: Sean Christopherson <seanjc@google.com>
To: Mingwei Zhang <mizhang@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
David Matlack <dmatlack@google.com>
Subject: Re: [PATCH v4 0/3] Extend KVM trace_kvm_nested_vmrun() to support VMX
Date: Tue, 30 Aug 2022 20:29:03 +0000 [thread overview]
Message-ID: <Yw5zD50fDb54zruw@google.com> (raw)
In-Reply-To: <20220825225755.907001-1-mizhang@google.com>
On Thu, Aug 25, 2022, Mingwei Zhang wrote:
> This patch set update trace_kvm_nested_vmrun() to support VMX. In
> addition, add the guest_pgd field to enrich the trace information.
...
> 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(-)
Some nits that I fixed up when applying (will respond to individual patches).
Pushed to branch `for_paolo/6.1` at:
https://github.com/sean-jc/linux.git
Unless you hear otherwise, it will make its way the official KVM tree "soon".
Note, the commit IDs are not guaranteed to be stable.
prev parent reply other threads:[~2022-08-30 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 22:57 [PATCH v4 0/3] Extend KVM trace_kvm_nested_vmrun() to support VMX Mingwei Zhang
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 ` 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=Yw5zD50fDb54zruw@google.com \
--to=seanjc@google.com \
--cc=dmatlack@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mizhang@google.com \
--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.