From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=53789 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PFsIM-00036G-DU for qemu-devel@nongnu.org; Tue, 09 Nov 2010 12:47:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PFsIL-0007Mq-3s for qemu-devel@nongnu.org; Tue, 09 Nov 2010 12:47:46 -0500 Received: from mail-qw0-f45.google.com ([209.85.216.45]:65022) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PFsIK-0007Ml-Vs for qemu-devel@nongnu.org; Tue, 09 Nov 2010 12:47:45 -0500 Received: by qwf6 with SMTP id 6so4853976qwf.4 for ; Tue, 09 Nov 2010 09:47:44 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <1289209443-2528-1-git-send-email-stefanha@linux.vnet.ibm.com> From: Blue Swirl Date: Tue, 9 Nov 2010 17:47:24 +0000 Message-ID: Subject: Re: [Qemu-devel] [PATCH] trace: Trace SCSI request lifecycle Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Stefan Hajnoczi , qemu-devel@nongnu.org On Mon, Nov 8, 2010 at 9:30 PM, Stefan Hajnoczi wrote: > On Mon, Nov 8, 2010 at 7:18 PM, Blue Swirl wrote: >> On Mon, Nov 8, 2010 at 9:44 AM, Stefan Hajnoczi >> wrote: >>> This patch adds trace events for SCSI request allocation, freeing, CDB >>> parsing, read, and write. =C2=A0These trace events can be used to instr= ument >>> the SCSI request lifecycle. >> >> How about converting also the DPRINTFs in hw/scsi-disk.c to tracepoints? > > Good idea. =C2=A0I don't understand the SCSI emulation well enough to tra= ce > the rest, so I couldn't do much besides a mechanical conversion. I also did only a mechanical conversion of Sparc32 devices earlier. I thought about removing or merging some of them, but then I considered that more tracepoints may be better to fewer. Is there a downside? There's a difference in the viewpoints. DPRINTFs may have been designed with debugging internal logic in mind. Alternatively we could be interested in only tracing the external interfaces. I don't think these views are in conflict since tracepoints are much more precise than DPRINTFs.