From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, 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,
scottwood@freescale.com, Hemant Kumar <hemant@linux.vnet.ibm.com>
Subject: [PATCH v5 2/2] perf,kvm/ppc: Add hcall related info to kvm_perf.h
Date: Thu, 16 Jul 2015 21:18:42 +0530 [thread overview]
Message-ID: <1437061722-15438-2-git-send-email-hemant@linux.vnet.ibm.com> (raw)
In-Reply-To: <1437061722-15438-1-git-send-email-hemant@linux.vnet.ibm.com>
To analyze the hcalls with perf, we need the hcall related tracepoints
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 as to what
tracepoints to look for if we are using "perf kvm stat record" to
collect guest hcall statistics.
Signed-off-by: Hemant Kumar <hemant@linux.vnet.ibm.com>
---
Changes:
- Not exporting the hcall related codes and names through uapi compared to
previous patch.
arch/powerpc/include/uapi/asm/kvm_perf_book3s.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/powerpc/include/uapi/asm/kvm_perf_book3s.h b/arch/powerpc/include/uapi/asm/kvm_perf_book3s.h
index 8c8d8c2..1378a8d 100644
--- a/arch/powerpc/include/uapi/asm/kvm_perf_book3s.h
+++ b/arch/powerpc/include/uapi/asm/kvm_perf_book3s.h
@@ -11,4 +11,8 @@
#define KVM_EXIT_TRACE "kvm_hv:kvm_guest_exit"
#define KVM_EXIT_REASON "trap"
+#define KVM_HCALL_ENTRY_TRACE "kvm_hv:kvm_hcall_enter"
+#define KVM_HCALL_EXIT_TRACE "kvm_hv:kvm_hcall_exit"
+#define KVM_HCALL_REASON "req"
+
#endif /* _ASM_POWERPC_KVM_PERF_BOOK3S_H */
--
1.9.3
next prev parent reply other threads:[~2015-07-16 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:48 [PATCH v5 1/2] perf,kvm/ppc: Add kvm_perf.h for powerpc Hemant Kumar
2015-07-16 15:48 ` Hemant Kumar [this message]
2015-07-16 20:10 ` Scott Wood
2015-07-29 10:37 ` Hemant Kumar
2015-07-29 22:22 ` Scott Wood
2015-07-31 8:55 ` Hemant Kumar
2015-07-31 23:42 ` Scott Wood
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=1437061722-15438-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).