[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4cdc179e652f8e2b2d7a069029101224779522a5.camel@wdc.com>
Date: Mon, 16 Apr 2018 21:30:54 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: "rostedt@...dmis.org" <rostedt@...dmis.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"beanhuo@...ron.com" <beanhuo@...ron.com>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"axboe@...nel.dk" <axboe@...nel.dk>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"mingo@...had.com" <mingo@...had.com>,
"rajatja@...gle.com" <rajatja@...gle.com>,
"jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>
Subject: Re: [RESEND PATCH v1 1/2] trace: events: scsi: Add tag in SCSI trace
events
On Mon, 2018-04-16 at 17:24 -0400, Steven Rostedt wrote:
> On Mon, 16 Apr 2018 20:49:12 +0000
> Bart Van Assche <Bart.VanAssche@....com> wrote:
>
> > Which tools process these strings? Has it been verified whether or not
> > the tools that process these strings still work fine with this patch
> > applied?
>
> Ideally, tools shouldn't process trace event strings, but I'm sure some
> do. :-/
>
> Getting libtraceevent out as a library is a high priority of mine, and
> hopefully I should get something out in a couple of months.
>
> Ideally, tools should parse the raw data and then new fields will not
> affect them.
Hello Steve,
The tool I'm most concerned about is blktrace. I'm not sure though how this
tool receives event data from the block layer core.
Thanks,
Bart.
Powered by blists - more mailing lists