[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180416172447.5166f854@gandalf.local.home>
Date: Mon, 16 Apr 2018 17:24:47 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Bart Van Assche <Bart.VanAssche@....com>
Cc: "beanhuo@...ron.com" <beanhuo@...ron.com>,
"jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.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>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"mingo@...had.com" <mingo@...had.com>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"rajatja@...gle.com" <rajatja@...gle.com>
Subject: Re: [RESEND PATCH v1 1/2] trace: events: scsi: Add tag in SCSI
trace events
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.
-- Steve
Powered by blists - more mailing lists