From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:43144) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIxIB-0006pi-Qt for qemu-devel@nongnu.org; Fri, 22 Mar 2013 04:25:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UIxI9-0005M0-DQ for qemu-devel@nongnu.org; Fri, 22 Mar 2013 04:25:39 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:42978) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UIxI8-0005LY-UV for qemu-devel@nongnu.org; Fri, 22 Mar 2013 04:25:37 -0400 Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 19DB63EE0BC for ; Fri, 22 Mar 2013 17:25:32 +0900 (JST) Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 03B1245DE52 for ; Fri, 22 Mar 2013 17:25:32 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id DF4CA45DE50 for ; Fri, 22 Mar 2013 17:25:31 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id CE8D21DB803F for ; Fri, 22 Mar 2013 17:25:31 +0900 (JST) Received: from G01JPEXCHYT27.g01.fujitsu.local (G01JPEXCHYT27.g01.fujitsu.local [10.128.193.110]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 39C881DB803E for ; Fri, 22 Mar 2013 17:25:31 +0900 (JST) Message-ID: <514C1560.1020406@jp.fujitsu.com> Date: Fri, 22 Mar 2013 17:25:04 +0900 From: Kazuya Saito MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [PATCH 0/5] Add some tracepoints for clarification of the cause of troubles List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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 hw/qdev.c | 3 +++ kvm-all.c | 5 +++++ qdev-monitor.c | 2 ++ trace-events | 14 ++++++++++++++ vl.c | 2 +- 5 files changed, 25 insertions(+), 1 deletions(-)