From: Paolo Bonzini <pbonzini@redhat.com>
To: Kazuya Saito <saito.kazuya@jp.fujitsu.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of the cause of troubles
Date: Fri, 22 Mar 2013 12:13:37 +0100 [thread overview]
Message-ID: <514C3CE1.3000100@redhat.com> (raw)
In-Reply-To: <514C1560.1020406@jp.fujitsu.com>
Il 22/03/2013 09:25, Kazuya Saito ha scritto:
> 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.
>
> Kazuya Saito (5):
> vl: add runstate_set tracepoint
> kvm-all: add kvm_ioctl, kvm_vm_ioctl, kvm_vcpu_ioctl tracepoints
> kvm-all: add kvm_run_exit tracepoint
> qdev: add qdev_{create,free} tracepoints
> qdev-monitor: add device_add tracepoint
I'm not sure 4-5 are that useful, but the first 3 patches are definitely
good stuff.
Paolo
next prev parent reply other threads:[~2013-03-22 11:13 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 ` [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 ` Paolo Bonzini [this message]
2013-03-26 7:13 ` [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of the cause of troubles 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=514C3CE1.3000100@redhat.com \
--to=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=saito.kazuya@jp.fujitsu.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.