All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <zanussi@kernel.org>
To: rostedt@goodmis.org
Cc: artem.bityutskiy@linux.intel.com, mhiramat@kernel.org,
	linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: [PATCH 0/4] tracing: Updates to dynamic event API
Date: Fri, 31 Jan 2020 15:55:30 -0600	[thread overview]
Message-ID: <cover.1580506712.git.zanussi@kernel.org> (raw)

Hi Steve,

This patchset adds some updates to the 'tracing: Add support for
in-kernel dynamic event API', on top of ftrace/core, addressing the
comments from v4 of that:

  - Consolidate the very similar functions
    synth_event_add_val/next_val() and inline find_synth_field(), as
    suggested by Steve

  - Replace the command-building code in dynevent_cmd with equivalent
    seq_buf functionality, as suggested by Steve

  - Move the check_arg callbacks from the arg objects and explicitly
    pass them to the add functions, as suggested by Masami

  - Get rid of a useless bit of code in dynevent_add_arg_pair() as
    suggested by Masami

With these changes the dynamic event test modules work fine and the
trigger selftests all pass.

Thanks,

Tom


The following changes since commit d380dcde9a07ca5de4805dee11f58a98ec0ad6ff:

  tracing: Fix now invalid var_ref_vals assumption in trace action (2020-01-31 12:59:26 -0500)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/zanussi/linux-trace.git ftrace/synth-event-gen-updates-v1

Tom Zanussi (4):
  tracing: Consolidate some synth_event_trace code
  tracing: Remove check_arg() callbacks from dynevent args
  tracing: Remove useless code in dynevent_arg_pair_add()
  tracing: Use seq_buf for building dynevent_cmd string

 include/linux/trace_events.h     |   4 +-
 kernel/trace/trace_dynevent.c    | 110 ++++++++++-----------------
 kernel/trace/trace_dynevent.h    |  11 ++-
 kernel/trace/trace_events_hist.c | 157 ++++++++++++++++-----------------------
 kernel/trace/trace_kprobe.c      |  12 +--
 5 files changed, 118 insertions(+), 176 deletions(-)

-- 
2.14.1


             reply	other threads:[~2020-01-31 21:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-31 21:55 Tom Zanussi [this message]
2020-01-31 21:55 ` [PATCH 1/4] tracing: Consolidate some synth_event_trace code Tom Zanussi
2020-01-31 22:43   ` Steven Rostedt
2020-01-31 22:47     ` Tom Zanussi
2020-01-31 23:00     ` Tom Zanussi
2020-01-31 23:33       ` Steven Rostedt
2020-02-04 10:00   ` kbuild test robot
2020-02-04 10:00   ` [RFC PATCH] tracing: __synth_event_add_val() can be static kbuild test robot
2020-01-31 21:55 ` [PATCH 2/4] tracing: Remove check_arg() callbacks from dynevent args Tom Zanussi
2020-02-01  7:28   ` Masami Hiramatsu
2020-01-31 21:55 ` [PATCH 3/4] tracing: Remove useless code in dynevent_arg_pair_add() Tom Zanussi
2020-02-01  7:28   ` Masami Hiramatsu
2020-01-31 21:55 ` [PATCH 4/4] tracing: Use seq_buf for building dynevent_cmd string Tom Zanussi
2020-02-01  7:48   ` 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=cover.1580506712.git.zanussi@kernel.org \
    --to=zanussi@kernel.org \
    --cc=artem.bityutskiy@linux.intel.com \
    --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 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.