From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, scottwood@freescale.com,
acme@kernel.org, mingo@kernel.org, mpe@ellerman.id.au,
sukadev@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com,
warrier@linux.vnet.ibm.com, srikar@linux.vnet.ibm.com,
paulus@samba.org, Hemant Kumar <hemant@linux.vnet.ibm.com>
Subject: [PATCH v6 2/2] perf, kvm/powerpc: Add hcall related info to kvm_perf.h
Date: Mon, 31 Aug 2015 12:18:01 +0530 [thread overview]
Message-ID: <1441003681-10259-2-git-send-email-hemant@linux.vnet.ibm.com> (raw)
In-Reply-To: <1441003681-10259-1-git-send-email-hemant@linux.vnet.ibm.com>
To analyze the hcalls with perf kvm stat, we need the hcall related
tracepoint information to be exported.
This patch adds hcall tracepoints "kvm_hv:kvm_hcall_enter" and
"kvm_hv:kvm_hcall_exit" to kvm_perf.h. So, perf will now know to look
for these tracepoints if "perf kvm stat record" is invoked to collect
guest hcall statistics.
Signed-off-by: Hemant Kumar <hemant@linux.vnet.ibm.com>
---
arch/powerpc/include/uapi/asm/kvm_perf.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/powerpc/include/uapi/asm/kvm_perf.h b/arch/powerpc/include/uapi/asm/kvm_perf.h
index 68f105e..2af6290 100644
--- a/arch/powerpc/include/uapi/asm/kvm_perf.h
+++ b/arch/powerpc/include/uapi/asm/kvm_perf.h
@@ -12,6 +12,10 @@
#define KVM_EXIT_TRACE_HV "kvm_hv:kvm_guest_exit"
#define KVM_EXIT_REASON_HV "trap"
+#define KVM_HCALL_ENTRY_TRACE_HV "kvm_hv:kvm_hcall_enter"
+#define KVM_HCALL_EXIT_TRACE_HV "kvm_hv:kvm_hcall_exit"
+#define KVM_HCALL_REASON_HV "req"
+
/* This is to shut the compiler up */
#define KVM_ENTRY_TRACE ""
#define KVM_EXIT_TRACE ""
--
1.9.3
next prev parent reply other threads:[~2015-08-31 6:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:48 [PATCH v6 1/2] perf,kvm/powerpc: Add kvm_perf.h for powerpc Hemant Kumar
2015-08-31 6:48 ` Hemant Kumar [this message]
2015-08-31 20:13 ` Arnaldo Carvalho de Melo
2015-09-01 6:48 ` Hemant Kumar
2015-09-04 20:51 ` Arnaldo Carvalho de Melo
2015-09-07 5:10 ` Michael Ellerman
2015-09-08 4:56 ` Hemant Kumar
2015-09-08 8:33 ` Michael Ellerman
2015-09-08 15:10 ` Arnaldo Carvalho de Melo
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=1441003681-10259-2-git-send-email-hemant@linux.vnet.ibm.com \
--to=hemant@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mingo@kernel.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=warrier@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).