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, stefanha@linux.vnet.ibm.com,
kvm@vger.kernel.org
Subject: [PATCH uq/master v2 0/2] Add some tracepoints for clarification of the cause of troubles
Date: Fri, 29 Mar 2013 13:24:25 +0900 [thread overview]
Message-ID: <51551779.9060403@jp.fujitsu.com> (raw)
This series adds tracepoints for helping us clarify the cause of
troubles. Virtualization on Linux is composed of some components such
as qemu, kvm, libvirt, and so on. So it is very important to clarify
firstly and swiftly the cause of troubles is on what component of
them. Although qemu has useful information of this because it stands
among kvm, libvirt and guest, it doesn't output the information by
trace or log system.
These patches add tracepoints which lead to reduce the time of the
clarification. We'd like to add the tracepoints as the first set
because, based on our experience, we've found out they must be useful
for an investigation in the future. Without those tracepoints,
we had a really hard time investigating a problem since the problem's
reproducibility was quite low and there was no clue in the dump of
qemu.
Changes from v1:
Add arg to kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints.
Add cpu_index to kvm_vcpu_ioctl, kvm_run_exit tracepoints.
Kazuya Saito (2):
kvm-all: add kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints
kvm-all: add kvm_run_exit tracepoint
kvm-all.c | 5 +++++
trace-events | 7 +++++++
2 files changed, 12 insertions(+), 0 deletions(-)
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, stefanha@linux.vnet.ibm.com,
kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH uq/master v2 0/2] Add some tracepoints for clarification of the cause of troubles
Date: Fri, 29 Mar 2013 13:24:25 +0900 [thread overview]
Message-ID: <51551779.9060403@jp.fujitsu.com> (raw)
This series adds tracepoints for helping us clarify the cause of
troubles. Virtualization on Linux is composed of some components such
as qemu, kvm, libvirt, and so on. So it is very important to clarify
firstly and swiftly the cause of troubles is on what component of
them. Although qemu has useful information of this because it stands
among kvm, libvirt and guest, it doesn't output the information by
trace or log system.
These patches add tracepoints which lead to reduce the time of the
clarification. We'd like to add the tracepoints as the first set
because, based on our experience, we've found out they must be useful
for an investigation in the future. Without those tracepoints,
we had a really hard time investigating a problem since the problem's
reproducibility was quite low and there was no clue in the dump of
qemu.
Changes from v1:
Add arg to kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints.
Add cpu_index to kvm_vcpu_ioctl, kvm_run_exit tracepoints.
Kazuya Saito (2):
kvm-all: add kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints
kvm-all: add kvm_run_exit tracepoint
kvm-all.c | 5 +++++
trace-events | 7 +++++++
2 files changed, 12 insertions(+), 0 deletions(-)
next reply other threads:[~2013-03-29 4:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 4:24 Kazuya Saito [this message]
2013-03-29 4:24 ` [Qemu-devel] [PATCH uq/master v2 0/2] Add some tracepoints for clarification of the cause of troubles 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 ` [PATCH uq/master v2 2/2] kvm-all: add kvm_run_exit tracepoint Kazuya Saito
2013-03-29 4:27 ` [Qemu-devel] " 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=51551779.9060403@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.