From: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 3/5] kvm-all: add kvm_run_exit tracepoint
Date: Fri, 22 Mar 2013 17:28:29 +0900 [thread overview]
Message-ID: <514C162D.10307@jp.fujitsu.com> (raw)
In-Reply-To: <514C1560.1020406@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 | 1 +
2 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kvm-all.c b/kvm-all.c
index da15623..29fca13 100644
--- a/kvm-all.c
+++ b/kvm-all.c
@@ -1576,6 +1576,7 @@ int kvm_cpu_exec(CPUArchState *env)
abort();
}
+ trace_kvm_run_exit(run->exit_reason);
switch (run->exit_reason) {
case KVM_EXIT_IO:
DPRINTF("handle_io\n");
diff --git a/trace-events b/trace-events
index 1af7060..c691ce4 100644
--- a/trace-events
+++ b/trace-events
@@ -1101,3 +1101,4 @@ migrate_set_state(int new_state) "new state %d"
kvm_ioctl(int type) "type %d"
kvm_vm_ioctl(int type) "type %d"
kvm_vcpu_ioctl(int type) "type %d"
+kvm_run_exit(uint32_t reason) "reason %d"
--
1.7.1
next prev parent reply other threads:[~2013-03-22 8:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 8:25 [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of the cause of troubles Kazuya Saito
2013-03-22 8:26 ` [Qemu-devel] [PATCH 1/5] vl: add runstate_set tracepoint Kazuya Saito
2013-03-22 11:13 ` Paolo Bonzini
2013-03-28 13:21 ` Stefan Hajnoczi
2013-03-22 8:27 ` [Qemu-devel] [PATCH 2/5] kvm-all: add kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints Kazuya Saito
2013-03-22 11:12 ` Paolo Bonzini
2013-03-22 8:28 ` Kazuya Saito [this message]
2013-03-22 11:12 ` [Qemu-devel] [PATCH 3/5] kvm-all: add kvm_run_exit tracepoint Paolo Bonzini
2013-03-22 8:29 ` [Qemu-devel] [PATCH 4/5] qdev: add qdev_{create,free} tracepoints Kazuya Saito
2013-03-27 11:03 ` [Qemu-devel] [PATCH 4/5] qdev: add qdev_{create, free} tracepoints Andreas Färber
2013-03-28 5:56 ` Kazuya Saito
2013-03-22 8:29 ` [Qemu-devel] [PATCH 5/5] qdev-monitor: add device_add tracepoint Kazuya Saito
2013-03-22 11:13 ` [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of the cause of troubles Paolo Bonzini
2013-03-26 7:13 ` Kazuya Saito
2013-03-26 7:15 ` Paolo Bonzini
2013-03-27 6:21 ` Kazuya Saito
2013-03-27 8:45 ` Paolo Bonzini
2013-03-28 5:53 ` Kazuya Saito
2013-03-28 8:52 ` Paolo Bonzini
2013-03-28 12:49 ` Anthony Liguori
2013-03-28 13:21 ` 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=514C162D.10307@jp.fujitsu.com \
--to=saito.kazuya@jp.fujitsu.com \
--cc=qemu-devel@nongnu.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 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.