public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: ehrhardt@linux.vnet.ibm.com
To: kvm@vger.kernel.org
Cc: hollisb@us.ibm.com, avi@qumranet.com, kvm-ppc@vger.kernel.org,
	ehrhardt@linux.vnet.ibm.com
Subject: [PATCH 0/5] kvmtrace: add powerpc support for KVM_TRACE
Date: Mon,  7 Jul 2008 15:56:48 +0200	[thread overview]
Message-ID: <1215439013-11480-1-git-send-email-ehrhardt@linux.vnet.ibm.com> (raw)

From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>

This series contains the revised patch set Jerone/Hollis posted last week
as well as the extension to use the KVM_TRACE infrastructure to trace
the embedded powerpc instruction emulation.

The series contains five patches (2 generic / 3 powerpc code):
Subject: [PATCH 1/5] kvmtrace: Remove use of bit fields in kvm trace structure v3
	Introducing a endian save way to store the flags event,tcs, num_data 
Subject: [PATCH 2/5] kvmtrace: make cycle calculation architecture aware
	let each architecture implement how to fill the trace cycle 64 bit field
Subject: [PATCH 3/5] kvmppc: kvmtrace: enable KVM_TRACE building for powerpc
	enable KVM_TRACE for powerpc in Kconfig/Makefile
Subject: [PATCH 4/5] kvmppc: kvmtrace: adds trace points for ppc tlb activity
	use KVM_TRACE to track tlb/shadow tlb activity on embedded powerpc
Subject: [PATCH 5/5] kvmppc: kvmtrace: trace powerpc instruction emulation
	use KVM_TRACE to track instruction emulation overhead

Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
---

[diffstat]
 arch/powerpc/kvm/emulate.c   |    4 ++++
 b/arch/powerpc/kvm/44x_tlb.c |   15 ++++++++++++++-
 b/arch/powerpc/kvm/Kconfig   |   11 +++++++++++
 b/arch/powerpc/kvm/Makefile  |    6 ++++--
 b/arch/powerpc/kvm/emulate.c |    4 ++++
 b/arch/powerpc/kvm/powerpc.c |   25 +++++++++++++++++++++++++
 b/arch/x86/kvm/x86.c         |    5 +++++
 b/include/linux/kvm.h        |   17 ++++++++++++++---
 b/include/linux/kvm_host.h   |    2 ++
 b/virt/kvm/kvm_trace.c       |   19 ++++++++++---------
 include/linux/kvm.h          |    4 ++++
 virt/kvm/kvm_trace.c         |    2 +-
 12 files changed, 98 insertions(+), 16 deletions(-)

             reply	other threads:[~2008-07-07 13:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-07 13:56 ehrhardt [this message]
2008-07-07 13:56 ` [PATCH 1/5] kvmtrace: Remove use of bit fields in kvm trace structure v3 ehrhardt
2008-07-07 13:56 ` [PATCH 2/5] kvmtrace: make cycle calculation architecture aware ehrhardt
2008-07-07 15:45   ` Hollis Blanchard
2008-07-09  8:25     ` Christian Ehrhardt
2008-07-07 16:37   ` Hollis Blanchard
2008-07-09  9:17     ` Christian Ehrhardt
2008-07-09 15:03       ` Hollis Blanchard
2008-07-10 10:22         ` Yang, Sheng
2008-07-10 10:24           ` Yang, Sheng
2008-07-10 13:32           ` Avi Kivity
2008-07-11  1:06             ` Yang, Sheng
2008-07-11  7:34             ` Carsten Otte
2008-07-11 15:19               ` Hollis Blanchard
2008-07-13 15:41               ` Avi Kivity
2008-07-14  7:44                 ` Christian Borntraeger
2008-07-07 13:56 ` [PATCH 3/5] kvmppc: kvmtrace: enable KVM_TRACE building for powerpc ehrhardt
2008-07-07 13:56 ` [PATCH 4/5] kvmppc: kvmtrace: adds trace points for ppc tlb activity v2 ehrhardt
2008-07-07 13:56 ` [PATCH 5/5] kvmppc: kvmtrace: trace powerpc instruction emulation ehrhardt

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=1215439013-11480-1-git-send-email-ehrhardt@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    /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