From: Jim Mattson <email@example.com> To: Krish Sadhukhan <firstname.lastname@example.org> Cc: kvm list <email@example.com>, Paolo Bonzini <firstname.lastname@example.org>, Sean Christopherson <email@example.com> Subject: Re: [PATCH 2/3] KVM: nVMX: Add a new VCPU statistic to show if VCPU is running nested guest Date: Wed, 12 May 2021 09:01:33 -0700 [thread overview] Message-ID: <CALMp9eTCgEG=kkQTn+g=DqniLq+RRmzp7jeK_iexoq++qiraxQ@mail.gmail.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Tue, May 11, 2021 at 7:37 PM Krish Sadhukhan <email@example.com> wrote: > > Add the following per-VCPU statistic to KVM debugfs to show if a given > VCPU is running a nested guest: > > nested_guest_running > > Also add this as a per-VM statistic to KVM debugfs to show the total number > of VCPUs running a nested guest in a given VM. > > Signed-off-by: Krish Sadhukhan <Krish.Sadhukhan@oracle.com> This is fine, but I don't really see its usefulness. OTOH, one statistic I would really like to see is how many vCPUs have *ever* run a nested guest.
next prev parent reply other threads:[~2021-05-12 16:41 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-12 1:47 [PATCH 0/3] KVM: nVMX: Add more statistics to KVM debugfs Krish Sadhukhan 2021-05-12 1:47 ` [PATCH 1/3] KVM: nVMX: Move 'nested_run' counter to enter_guest_mode() Krish Sadhukhan 2021-05-12 18:30 ` Sean Christopherson 2021-05-13 16:02 ` Dongli Zhang 2021-05-12 1:47 ` [PATCH 2/3] KVM: nVMX: Add a new VCPU statistic to show if VCPU is running nested guest Krish Sadhukhan 2021-05-12 16:01 ` Jim Mattson [this message] 2021-05-12 17:56 ` Krish Sadhukhan 2021-05-12 17:59 ` Jim Mattson 2021-05-12 18:19 ` Sean Christopherson 2021-05-12 1:47 ` [PATCH 3/3] KVM: x86: Add a new VM statistic to show number of VCPUs created in a given VM Krish Sadhukhan
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='CALMp9eTCgEG=kkQTn+g=DqniLq+RRmzp7jeK_iexoq++qiraxQ@mail.gmail.com' \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH 2/3] KVM: nVMX: Add a new VCPU statistic to show if VCPU is running nested guest' \ /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
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).