From: Maxim Levitsky <mlevitsk@redhat.com>
To: kvm@vger.kernel.org
Cc: x86@kernel.org, Dave Hansen <dave.hansen@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Sean Christopherson <seanjc@google.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] KVM: x86: tracepoint updates
Date: Wed, 30 Oct 2024 17:21:49 -0400 [thread overview]
Message-ID: <d59b923ebd369415056c80b99ca4e0f75d60fa84.camel@redhat.com> (raw)
In-Reply-To: <20240910200350.264245-1-mlevitsk@redhat.com>
On Tue, 2024-09-10 at 16:03 -0400, Maxim Levitsky wrote:
> This patch series is intended to add some selected information
> to the kvm tracepoints to make it easier to gather insights about
> running nested guests.
>
> This patch series was developed together with a new x86 performance analysis tool
> that I developed recently (https://gitlab.com/maximlevitsky/kvmon)
> which aims to be a better kvm_stat, and allows you at glance
> to see what is happening in a VM, including nesting.
>
> V5: rebased on top of recent changes
>
> Best regards,
> Maxim Levitsky
>
> Maxim Levitsky (3):
> KVM: x86: add more information to the kvm_entry tracepoint
> KVM: x86: add information about pending requests to kvm_exit
> tracepoint
> KVM: x86: add new nested vmexit tracepoints
>
> arch/x86/include/asm/kvm-x86-ops.h | 1 +
> arch/x86/include/asm/kvm_host.h | 5 +-
> arch/x86/kvm/svm/nested.c | 22 ++++++
> arch/x86/kvm/svm/svm.c | 17 +++++
> arch/x86/kvm/trace.h | 107 ++++++++++++++++++++++++++---
> arch/x86/kvm/vmx/main.c | 1 +
> arch/x86/kvm/vmx/nested.c | 27 ++++++++
> arch/x86/kvm/vmx/vmx.c | 11 +++
> arch/x86/kvm/vmx/x86_ops.h | 4 ++
> arch/x86/kvm/x86.c | 3 +
> 10 files changed, 189 insertions(+), 9 deletions(-)
>
> --
> 2.26.3
>
>
Hi,
A very gentle ping on this patch series.
Best regards,
Maxim Levitsky
next prev parent reply other threads:[~2024-10-30 21:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 20:03 Maxim Levitsky
2024-09-10 20:03 ` [PATCH v5 1/3] KVM: x86: add more information to the kvm_entry tracepoint Maxim Levitsky
2024-12-18 20:53 ` Sean Christopherson
2024-09-10 20:03 ` [PATCH v5 2/3] KVM: x86: add information about pending requests to kvm_exit tracepoint Maxim Levitsky
2024-09-10 20:03 ` [PATCH v5 3/3] KVM: x86: add new nested vmexit tracepoints Maxim Levitsky
2024-12-18 21:14 ` [PATCH v5 3/3] KVM: x86: add new nested vmexit tracepointsg Sean Christopherson
2024-12-19 17:33 ` [PATCH v5 3/3] KVM: x86: add new nested vmexit tracepoints Paolo Bonzini
2024-12-19 17:49 ` Maxim Levitsky
2024-12-19 18:02 ` Paolo Bonzini
2025-01-16 22:53 ` Sean Christopherson
2024-10-30 21:21 ` Maxim Levitsky [this message]
2024-11-22 1:04 ` [PATCH v5 0/3] KVM: x86: tracepoint updates Maxim Levitsky
2024-12-19 2:40 ` 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=d59b923ebd369415056c80b99ca4e0f75d60fa84.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@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 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®