qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of t


From: Paolo Bonzini
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
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]