From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: kvm@vger.kernel.org
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jim Mattson <jmattson@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Emanuele Giuseppe Esposito <e.emanuelegiuseppe@gmail.com>,
David Rientjes <rientjes@google.com>,
Jonathan Adams <jwadams@google.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org,
kvm-ppc@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-s390@vger.kernel.org, linux-fsdevel@vger.kernel.org,
netdev@vger.kernel.org,
Emanuele Giuseppe Esposito <eesposit@redhat.com>
Subject: [PATCH v3 6/7] [not for merge] kvm: example of stats_fs_value show function
Date: Tue, 26 May 2020 13:03:16 +0200 [thread overview]
Message-ID: <20200526110318.69006-7-eesposit@redhat.com> (raw)
In-Reply-To: <20200526110318.69006-1-eesposit@redhat.com>
Add an example of the show function using the mp_state value.
mp_state is an enum that represents the VCPU state,
so instead of displaying its integer representation,
the show function takes care of translating the integer into a
more meaningful string representation.
The VCPU status is shown in the kvm/<vmid>/vcpu<cpuid>/mp_state file
Signed-off-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>
---
arch/x86/kvm/stats_fs.c | 54 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 54 insertions(+)
diff --git a/arch/x86/kvm/stats_fs.c b/arch/x86/kvm/stats_fs.c
index f6edebb9c559..902be18562da 100644
--- a/arch/x86/kvm/stats_fs.c
+++ b/arch/x86/kvm/stats_fs.c
@@ -39,11 +39,65 @@ struct stats_fs_value stats_fs_vcpu_arch_tsc_frac[] = {
{ NULL } /* base is &kvm_tsc_scaling_ratio_frac_bits */
};
+char *stats_fs_vcpu_get_mpstate(uint64_t state)
+{
+ char *state_str;
+
+ state_str = kzalloc(20, GFP_KERNEL);
+ if (!state_str)
+ return ERR_PTR(-ENOMEM);
+
+ switch (state) {
+ case KVM_MP_STATE_RUNNABLE:
+ strcpy(state_str, "RUNNABLE");
+ break;
+ case KVM_MP_STATE_UNINITIALIZED:
+ strcpy(state_str, "UNINITIALIZED");
+ break;
+ case KVM_MP_STATE_INIT_RECEIVED:
+ strcpy(state_str, "INIT_RECEIVED");
+ break;
+ case KVM_MP_STATE_HALTED:
+ strcpy(state_str, "HALTED");
+ break;
+ case KVM_MP_STATE_SIPI_RECEIVED:
+ strcpy(state_str, "SIPI_RECEIVED");
+ break;
+ case KVM_MP_STATE_STOPPED:
+ strcpy(state_str, "STOPPED");
+ break;
+ case KVM_MP_STATE_CHECK_STOP:
+ strcpy(state_str, "CHECK_STOP");
+ break;
+ case KVM_MP_STATE_OPERATING:
+ strcpy(state_str, "OPERATING");
+ break;
+ case KVM_MP_STATE_LOAD:
+ strcpy(state_str, "LOAD");
+ break;
+ default:
+ strcpy(state_str, "UNRECOGNIZED");
+ break;
+ }
+
+ return state_str;
+}
+
+struct stats_fs_value stats_fs_vcpu_mp_state[] = {
+ VCPU_ARCH_STATS_FS("mp_state", kvm_vcpu_arch, mp_state,
+ .type = &stats_fs_type_u32,
+ .show = stats_fs_vcpu_get_mpstate),
+ { NULL }
+};
+
void kvm_arch_create_vcpu_stats_fs(struct kvm_vcpu *vcpu)
{
stats_fs_source_add_values(vcpu->stats_fs_src, stats_fs_vcpu_tsc_offset,
&vcpu->arch, 0);
+ stats_fs_source_add_values(vcpu->stats_fs_src, stats_fs_vcpu_mp_state,
+ &vcpu->arch, 0);
+
if (lapic_in_kernel(vcpu))
stats_fs_source_add_values(vcpu->stats_fs_src,
stats_fs_vcpu_arch_lapic_timer,
--
2.25.4
next prev parent reply other threads:[~2020-05-26 11:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 11:03 [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 1/7] stats_fs API: create, add and remove stats_fs sources and values Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 2/7] documentation for stats_fs Emanuele Giuseppe Esposito
2020-06-04 0:23 ` Randy Dunlap
2020-06-04 15:34 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 3/7] kunit: tests for stats_fs API Emanuele Giuseppe Esposito
2020-05-27 10:05 ` Alan Maguire
2020-05-27 13:26 ` Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 4/7] stats_fs fs: virtual fs to show stats to the end-user Emanuele Giuseppe Esposito
2020-05-26 11:03 ` [PATCH v3 5/7] kvm_main: replace debugfs with stats_fs Emanuele Giuseppe Esposito
2020-05-26 11:03 ` Emanuele Giuseppe Esposito [this message]
2020-05-26 11:03 ` [PATCH v3 7/7] [not for merge] netstats: example use of stats_fs API Emanuele Giuseppe Esposito
2020-05-26 14:16 ` Andrew Lunn
2020-05-26 15:45 ` Emanuele Giuseppe Esposito
2020-05-26 22:31 ` [PATCH v3 0/7] Statsfs: a new ram-based file system for Linux kernel statistics Jakub Kicinski
2020-05-27 13:14 ` Emanuele Giuseppe Esposito
2020-05-27 13:33 ` Andrew Lunn
2020-05-27 15:00 ` Paolo Bonzini
2020-05-27 20:23 ` Jakub Kicinski
2020-05-27 21:07 ` Paolo Bonzini
2020-05-27 21:27 ` Jakub Kicinski
2020-05-27 21:44 ` Paolo Bonzini
2020-05-27 22:21 ` David Ahern
2020-05-28 5:22 ` Paolo Bonzini
2020-05-27 21:17 ` Andrew Lunn
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=20200526110318.69006-7-eesposit@redhat.com \
--to=eesposit@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=e.emanuelegiuseppe@gmail.com \
--cc=jmattson@google.com \
--cc=jwadams@google.com \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=viro@zeniv.linux.org.uk \
/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).