From: Tom Zanussi <zanussi@kernel.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: rostedt@goodmis.org, bristot@kernel.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH 0/1] tracing: Provide more parseable hist trigger output
Date: Fri, 13 Aug 2021 10:31:03 -0500 [thread overview]
Message-ID: <42a2672432301de9beee593765bb49f739ce493a.camel@kernel.org> (raw)
In-Reply-To: <20210813182436.0ca56fe333a80fb7188f0b14@kernel.org>
Hi Masami,
On Fri, 2021-08-13 at 18:24 +0900, Masami Hiramatsu wrote:
> Hi Tom,
>
> On Thu, 12 Aug 2021 17:43:23 -0500
> Tom Zanussi <zanussi@kernel.org> wrote:
>
> > Hi Steve and Daniel,
> >
> > Following our discussion last week about more parseable hist
> > trigger
> > output, I started trying to implement the 'csv' output you had
> > mentioned, but realized that since it was more than just table
> > output
> > that was needed, JSON would be a better fit, so implemented that in
> > this patch instead.
>
> This seems really good feature! BTW, what about adding an tracing
> option to switch the hist output format?
> e.g.
>
> $ echo 1 > /sys/kernel/tracing/options/hist-json
>
> This will no need to add additional pseudo file but just add an
> option to
> the ftrace.
>
That sounds like a good idea, thanks for the suggestion!
Tom
next prev parent reply other threads:[~2021-08-13 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 22:43 [PATCH 0/1] tracing: Provide more parseable hist trigger output Tom Zanussi
2021-08-12 22:43 ` [PATCH 1/1] tracing: Add hist_json event file Tom Zanussi
2021-08-13 2:36 ` [PATCH 0/1] tracing: Provide more parseable hist trigger output Steven Rostedt
2021-08-13 9:24 ` Masami Hiramatsu
2021-08-13 15:31 ` Tom Zanussi [this message]
2021-08-16 15:25 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42a2672432301de9beee593765bb49f739ce493a.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox