All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Tom Zanussi <tom.zanussi@linux.intel.com>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] tracing: Add 'hash' event trigger command
Date: Fri, 28 Mar 2014 09:54:55 -0700	[thread overview]
Message-ID: <87lhvunu00.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <b81b0860d2915c0b562863fce889249dad080922.1395894625.git.tom.zanussi@linux.intel.com> (Tom Zanussi's message of "Wed, 26 Mar 2014 23:54:07 -0500")

Tom Zanussi <tom.zanussi@linux.intel.com> writes:

> Hash triggers allow users to continually hash events which can then be
> dumped later by simply reading the trigger file.  This is done
> strictly via one-liners and without any kind of programming language.

I read through the whole thing. I think I got it somewhere near the end,
but it was quite difficult. What really confuses me is your
use of the "hash" term. I believe the established term for these
kind of data operations is "histogram". How about calling it that.

Overall it seems useful, but it's not fully clear to me why it needs
to be done in the kernel and not an analysis tool?

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2014-03-28 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27  4:54 [PATCH 0/5] tracing: Hash triggers Tom Zanussi
2014-03-27  4:54 ` [PATCH 1/5] tracing: Make ftrace_event_field checking functions available Tom Zanussi
2014-03-27  4:54 ` [PATCH 2/5] tracing: Add event record param to trigger_ops.func() Tom Zanussi
2014-03-27  4:54 ` [PATCH 3/5] tracing: Add get_syscall_name() Tom Zanussi
2014-03-27  4:54 ` [PATCH 4/5] tracing: Add hash trigger to Documentation Tom Zanussi
2014-03-27  4:54 ` [PATCH 5/5] tracing: Add 'hash' event trigger command Tom Zanussi
2014-03-28 16:54   ` Andi Kleen [this message]
2014-03-28 19:13     ` Tom Zanussi
2014-04-03  8:59   ` Masami Hiramatsu
2014-04-03 22:43     ` Tom Zanussi
2014-04-04  1:44       ` Masami Hiramatsu

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=87lhvunu00.fsf@tassilo.jf.intel.com \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tom.zanussi@linux.intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.