All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
	"stefanha@linux.vnet.ibm.com" <stefanha@linux.vnet.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [PATCH uq/master v2 2/2] kvm-all: add kvm_run_exit tracepoint
Date: Fri, 29 Mar 2013 13:27:52 +0900	[thread overview]
Message-ID: <51551848.3040207@jp.fujitsu.com> (raw)
In-Reply-To: <51551779.9060403@jp.fujitsu.com>

This patch enable us to know exit reason of KVM_RUN. It will help us
know where the trouble is caused.

Signed-off-by: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
---
 kvm-all.c    |    1 +
 trace-events |    2 ++
 2 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/kvm-all.c b/kvm-all.c
index fdb099c..325f5e7 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -1574,6 +1574,7 @@ int kvm_cpu_exec(CPUArchState *env)
             abort();
         }

+        trace_kvm_run_exit(cpu->cpu_index, run->exit_reason);
         switch (run->exit_reason) {
         case KVM_EXIT_IO:
             DPRINTF("handle_io\n");
diff --git a/trace-events b/trace-events
index 3023744..8fd6e80 100644
--- a/trace-events
+++ b/trace-events
@@ -1106,3 +1106,5 @@ migrate_set_state(int new_state) "new state %d"
 kvm_ioctl(int type, void *arg) "type %d, arg %p"
 kvm_vm_ioctl(int type, void *arg) "type %d, arg %p"
 kvm_vcpu_ioctl(int cpu_index, int type, void *arg) "cpu_index %d, type %d, arg %p"
+kvm_run_exit(int cpu_index, uint32_t reason) "cpu_index %d, reason %d"
+
-- 
1.7.1




WARNING: multiple messages have this Message-ID (diff)
From: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	"aliguori@us.ibm.com" <aliguori@us.ibm.com>,
	"stefanha@linux.vnet.ibm.com" <stefanha@linux.vnet.ibm.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: [Qemu-devel] [PATCH uq/master v2 2/2] kvm-all: add kvm_run_exit tracepoint
Date: Fri, 29 Mar 2013 13:27:52 +0900	[thread overview]
Message-ID: <51551848.3040207@jp.fujitsu.com> (raw)
In-Reply-To: <51551779.9060403@jp.fujitsu.com>

This patch enable us to know exit reason of KVM_RUN. It will help us
know where the trouble is caused.

Signed-off-by: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
---
 kvm-all.c    |    1 +
 trace-events |    2 ++
 2 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/kvm-all.c b/kvm-all.c
index fdb099c..325f5e7 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -1574,6 +1574,7 @@ int kvm_cpu_exec(CPUArchState *env)
             abort();
         }

+        trace_kvm_run_exit(cpu->cpu_index, run->exit_reason);
         switch (run->exit_reason) {
         case KVM_EXIT_IO:
             DPRINTF("handle_io\n");
diff --git a/trace-events b/trace-events
index 3023744..8fd6e80 100644
--- a/trace-events
+++ b/trace-events
@@ -1106,3 +1106,5 @@ migrate_set_state(int new_state) "new state %d"
 kvm_ioctl(int type, void *arg) "type %d, arg %p"
 kvm_vm_ioctl(int type, void *arg) "type %d, arg %p"
 kvm_vcpu_ioctl(int cpu_index, int type, void *arg) "cpu_index %d, type %d, arg %p"
+kvm_run_exit(int cpu_index, uint32_t reason) "cpu_index %d, reason %d"
+
-- 
1.7.1

  parent reply	other threads:[~2013-03-29  4:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-29  4:24 [PATCH uq/master v2 0/2] Add some tracepoints for clarification of the cause of troubles Kazuya Saito
2013-03-29  4:24 ` [Qemu-devel] " Kazuya Saito
2013-03-29  4:27 ` [PATCH uq/master v2 1/2] kvm-all: add kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints Kazuya Saito
2013-03-29  4:27   ` [Qemu-devel] " Kazuya Saito
2013-03-29  4:27 ` Kazuya Saito [this message]
2013-03-29  4:27   ` [Qemu-devel] [PATCH uq/master v2 2/2] kvm-all: add kvm_run_exit tracepoint Kazuya Saito
2013-03-29  8:09 ` [PATCH uq/master v2 0/2] Add some tracepoints for clarification of the cause of troubles Paolo Bonzini
2013-03-29  8:09   ` [Qemu-devel] " Paolo Bonzini
2013-04-08 15:48 ` Stefan Hajnoczi
2013-04-08 15:48   ` Stefan Hajnoczi

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=51551848.3040207@jp.fujitsu.com \
    --to=saito.kazuya@jp.fujitsu.com \
    --cc=aliguori@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.