From: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/5] vl: add runstate_set tracepoint
Date: Fri, 22 Mar 2013 17:26:59 +0900 [thread overview]
Message-ID: <514C15D3.1020003@jp.fujitsu.com> (raw)
In-Reply-To: <514C1560.1020406@jp.fujitsu.com>
This patch enables us to know RunState transition. It will be userful
for investigation when the trouble occured in special event such like
live migration, shutdown, suspend, and so on.
Signed-off-by: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
---
trace-events | 1 +
vl.c | 2 +-
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/trace-events b/trace-events
index d6a847d..1e352a7 100644
--- a/trace-events
+++ b/trace-events
@@ -474,6 +474,7 @@ scsi_request_sense(int target, int lun, int tag) "target %d lun %d tag %d"
# vl.c
vm_state_notify(int running, int reason) "running %d reason %d"
load_file(const char *name, const char *path) "name %s location %s"
+runstate_set(int new_state) "new state %d"
# block/qcow2.c
qcow2_writev_start_req(void *co, int64_t sector, int nb_sectors) "co %p sector %" PRIx64 " nb_sectors %d"
diff --git a/vl.c b/vl.c
index a621aec..4bd3671 100644
--- a/vl.c
+++ b/vl.c
@@ -638,7 +638,7 @@ void runstate_set(RunState new_state)
RunState_lookup[new_state]);
abort();
}
-
+ trace_runstate_set(new_state);
current_run_state = new_state;
}
--
1.7.1
next prev parent reply other threads:[~2013-03-22 8:27 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 ` Kazuya Saito [this message]
2013-03-22 11:13 ` [Qemu-devel] [PATCH 1/5] vl: add runstate_set tracepoint 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 ` [Qemu-devel] [PATCH 3/5] kvm-all: add kvm_run_exit tracepoint Kazuya Saito
2013-03-22 11:12 ` 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=514C15D3.1020003@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 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).