From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42273) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULQs6-0004dZ-Fp for qemu-devel@nongnu.org; Fri, 29 Mar 2013 00:25:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULQs3-0007eU-M1 for qemu-devel@nongnu.org; Fri, 29 Mar 2013 00:24:58 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:36174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULQs3-0007db-5o for qemu-devel@nongnu.org; Fri, 29 Mar 2013 00:24:55 -0400 Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id 392803EE0BD for ; Fri, 29 Mar 2013 13:24:52 +0900 (JST) Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id 1213545DE51 for ; Fri, 29 Mar 2013 13:24:52 +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 DCCB445DE4F for ; Fri, 29 Mar 2013 13:24:51 +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 CFAF4E08003 for ; Fri, 29 Mar 2013 13:24:51 +0900 (JST) Received: from g01jpexchkw10.g01.fujitsu.local (g01jpexchkw10.g01.fujitsu.local [10.0.194.49]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 88A8A1DB8037 for ; Fri, 29 Mar 2013 13:24:51 +0900 (JST) Message-ID: <51551779.9060403@jp.fujitsu.com> Date: Fri, 29 Mar 2013 13:24:25 +0900 From: Kazuya Saito MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [PATCH uq/master v2 0/2] 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" Cc: Paolo Bonzini , aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com, kvm@vger.kernel.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. 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(-)