From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: daniel.wagner@bmw-carit.de, masami.hiramatsu.pt@hitachi.com,
namhyung@kernel.org, josh@joshtriplett.org, andi@firstfloor.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 00/10] tracing: 'hist' triggers
Date: Thu, 21 May 2015 09:29:15 -0500 [thread overview]
Message-ID: <1432218555.27713.23.camel@picadillo> (raw)
In-Reply-To: <20150521095528.68c6c361@gandalf.local.home>
On Thu, 2015-05-21 at 09:55 -0400, Steven Rostedt wrote:
> On Wed, 20 May 2015 16:19:47 -0500
> Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
>
>
> > There are a couple of important bits of functionality that were
> > present in v1 but not yet reimplemented in v5.
> >
>
> I take it that "yet" means they can still be implemented on top of v5
> right? Without breaking backward compatibility of the interface?
>
Yeah, that's referring to compound keys and sorting on multiple keys.
At this point, I'm so close to having that and have previous code to
work from, so I'll just cook up a v6 without those caveats, and we don't
have to worry about it. Give me a couple of days to get to that..
Tom
> Thanks for doing this, I'll try to get some time to look closer at the
> patches.
>
> -- Steve
next prev parent reply other threads:[~2015-05-21 14:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 21:19 [PATCH v5 00/10] tracing: 'hist' triggers Tom Zanussi
2015-05-20 21:19 ` [PATCH 01/10] tracing: Update cond flag when enabling or disabling a trigger Tom Zanussi
2015-05-21 7:21 ` Masami Hiramatsu
2015-05-20 21:19 ` [PATCH v5 02/10] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 03/10] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 04/10] tracing: Add get_syscall_name() Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 05/10] tracing: Add a per-event-trigger 'paused' field Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 06/10] trace: Add lock-free tracing_map Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 07/10] tracing: Add 'hist' event trigger command Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 08/10] tracing: Add enable_hist/disable_hist triggers Tom Zanussi
2015-05-20 21:19 ` [PATCH v5 09/10] tracing: Add 'hist' trigger Documentation Tom Zanussi
2015-05-20 21:19 ` [PATCH 10/10][RFC] ftrace: Add function_hist tracer Tom Zanussi
2015-05-21 8:08 ` [PATCH v5 00/10] tracing: 'hist' triggers Masami Hiramatsu
2015-05-21 15:26 ` Tom Zanussi
2015-05-21 21:50 ` Masami Hiramatsu
2015-05-21 13:55 ` Steven Rostedt
2015-05-21 14:29 ` Tom Zanussi [this message]
2015-05-21 14:31 ` Steven Rostedt
2015-05-21 14:37 ` Tom Zanussi
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=1432218555.27713.23.camel@picadillo \
--to=tom.zanussi@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=daniel.wagner@bmw-carit.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=namhyung@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