From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33221) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAjul-0007Oj-Rj for qemu-devel@nongnu.org; Fri, 15 Apr 2011 10:22:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QAjuk-000678-OF for qemu-devel@nongnu.org; Fri, 15 Apr 2011 10:22:27 -0400 Received: from mail-pw0-f45.google.com ([209.85.160.45]:52713) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QAjuk-000673-G0 for qemu-devel@nongnu.org; Fri, 15 Apr 2011 10:22:26 -0400 Received: by pwj6 with SMTP id 6so1392765pwj.4 for ; Fri, 15 Apr 2011 07:22:25 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <4DA8549B.2020301@redhat.com> Date: Fri, 15 Apr 2011 16:22:19 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1302873840-17161-1-git-send-email-pbonzini@redhat.com> <1302873840-17161-3-git-send-email-pbonzini@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 2/2] add tracing of scsi requests List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: qemu-devel@nongnu.org On 04/15/2011 04:15 PM, Stefan Hajnoczi wrote: > On Fri, Apr 15, 2011 at 2:24 PM, Paolo Bonzini wrote: >> +disable scsi_req_parsed(int target, int lun, int tag, int cmd, const char *cmdname, int mode, int xfer, uint64_t lba) "target %d lun %d tag %d command %d (%s) dir %d length %d lba %"PRIu64"" > > Tracing strings isn't possible with all trace backends, so we should > avoid it. It works fine with stderr but other trace backends may not > be in the same address space (they are unable to dereference pointers > to strings) or simply not have the ability to record variable-length > data. Yeah, I saw them. What happens with the other backends? Do they crash or do they just record bogus data? If the latter (like IIRC simpletrace), I'd really like to keep the string. It is duplicating the cmd argument, so it is possible to work without it on non-stderr backends; with stderr OTOH the human-readable version is really useful before you have learnt the SCSI spec by heart. :) Paolo