From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35545) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKO5R-0006D2-P5 for qemu-devel@nongnu.org; Tue, 26 Mar 2013 03:14:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UKO5L-00028y-AU for qemu-devel@nongnu.org; Tue, 26 Mar 2013 03:14:25 -0400 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:57629) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UKO5K-00028b-PP for qemu-devel@nongnu.org; Tue, 26 Mar 2013 03:14:19 -0400 Received: from m1.gw.fujitsu.co.jp (unknown [10.0.50.71]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id EE7BA3EE0AE for ; Tue, 26 Mar 2013 16:14:13 +0900 (JST) Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id D5F6A45DE5C for ; Tue, 26 Mar 2013 16:14:13 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id BB16B45DE55 for ; Tue, 26 Mar 2013 16:14:13 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id A10B7E08006 for ; Tue, 26 Mar 2013 16:14:13 +0900 (JST) Received: from G01JPEXCHYT27.g01.fujitsu.local (G01JPEXCHYT27.g01.fujitsu.local [10.128.193.110]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 5109CE08005 for ; Tue, 26 Mar 2013 16:14:13 +0900 (JST) Message-ID: <51514AA1.9040008@jp.fujitsu.com> Date: Tue, 26 Mar 2013 16:13:37 +0900 From: Kazuya Saito MIME-Version: 1.0 References: <514C1560.1020406@jp.fujitsu.com> <514C3CE1.3000100@redhat.com> In-Reply-To: <514C3CE1.3000100@redhat.com> Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit Subject: Re: [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: Paolo Bonzini Cc: qemu-devel@nongnu.org (2013/03/22 20:13), Paolo Bonzini wrote: > 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. Thanks. I'll modify the patch you pointed out about CPU number and re-post it. I'd like to add tracepoints to the virtual device creation/deletion part. I had an issue that when a Windows guest OS booted up, it didn't have a virtual NIC device which it should have had. It took us time to figure out which the guest OS or the QEMU had the issue. If I have had the tracepoints in the virtual device creation/deletion should have eased the situation much better. Kazuya