linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hemant Kumar <hemant@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: maddy@linux.vnet.ibm.com, srikar@linux.vnet.ibm.com,
	anton@au1.ibm.com, linux-kernel@vger.kernel.org, agraf@suse.de,
	paulus@samba.org, warrier@linux.vnet.ibm.com
Subject: [PATCH v1 0/2] perf/kvm: perf-kvm-stat on powerpc
Date: Fri, 27 Feb 2015 15:13:26 +0530	[thread overview]
Message-ID: <20150227093649.6367.15679.stgit@localhost.localdomain> (raw)

perf kvm stat record/report which can be used to analyze KVM related statistics
isn't enabled on powerpc. This patchset enables "perf kvm stat" on powerpc.
The first patch enables perf kvm stat record and report to report kvm exits.

"record" enables recording of the tracepoints: kvm_hv:kvm_guest_enter and
kvm_hv:kvm_guest_exit in the first patch and kvm_hv:kvm_hcall_enter and
kvm_hv:kvm_hcall_exit in the second patch.

This command can be used to record kvm events on the host:
# perf kvm stat record -a

To report the kvm guest related exit events, use:
# perf kvm stat report
or
# perf kvm stat report --event=vmexit

This should show the exit events along with the exit reasons.

The second patch in this series adds support to show the hcall events too with:
# perf kvm stat report --event=syscall

---

Hemant Kumar (1):
      perf/kvm: perf-kvm-stat to report syscalls

Srikar Dronamraju (1):
      perf/kvm: Enable perf-kvm-stat record/report on powerpc


 arch/powerpc/include/asm/hvcall.h            |  120 -------------------------
 arch/powerpc/include/uapi/asm/hcall_codes.h  |  123 ++++++++++++++++++++++++++
 arch/powerpc/include/uapi/asm/kvm_perf.h     |   19 ++++
 arch/powerpc/include/uapi/asm/trace_book3s.h |   33 +++++++
 arch/powerpc/include/uapi/asm/trace_hcall.h  |  122 ++++++++++++++++++++++++++
 arch/powerpc/kvm/trace_book3s.h              |   32 -------
 arch/powerpc/kvm/trace_hv.h                  |  119 -------------------------
 arch/powerpc/kvm/trace_pr.h                  |    2 
 tools/perf/arch/powerpc/Makefile             |    1 
 tools/perf/arch/powerpc/util/Build           |    1 
 tools/perf/arch/powerpc/util/kvm-stat.c      |   94 ++++++++++++++++++++
 11 files changed, 398 insertions(+), 268 deletions(-)
 create mode 100644 arch/powerpc/include/uapi/asm/hcall_codes.h
 create mode 100644 arch/powerpc/include/uapi/asm/kvm_perf.h
 create mode 100644 arch/powerpc/include/uapi/asm/trace_book3s.h
 create mode 100644 arch/powerpc/include/uapi/asm/trace_hcall.h
 delete mode 100644 arch/powerpc/kvm/trace_book3s.h
 create mode 100644 tools/perf/arch/powerpc/util/kvm-stat.c

--

             reply	other threads:[~2015-02-27  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  9:43 Hemant Kumar [this message]
2015-02-27  9:43 ` [PATCH v1 1/2] perf/kvm: Enable perf-kvm-stat record/report on powerpc Hemant Kumar
2015-02-27  9:44 ` [PATCH v1 2/2] perf/kvm: perf-kvm-stat to report syscalls Hemant Kumar
2015-03-24  6:48 ` [PATCH v1 0/2] perf/kvm: perf-kvm-stat on powerpc Hemant Kumar
2015-03-24 13:17   ` Michael Ellerman

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=20150227093649.6367.15679.stgit@localhost.localdomain \
    --to=hemant@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=anton@au1.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=srikar@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).