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/3] tracing: Synthetic event fixes and updates
Date: Mon, 10 Feb 2020 17:06:47 -0600 [thread overview]
Message-ID: <cover.1581374549.git.zanussi@kernel.org> (raw)
Hi Steve,
I noticed a couple bugs while creating a patch consolidating the
synthetic event trace() functions. Here are the two bugfixes along
with the consolidated trace patch.
The first patch adds a missing ring_buffer_nest_end() in an error
case, and the second removes unnecessary error returns when an event
is soft disabled.
The third patch consolidates the common code in synth_event_trace_array(),
synth_event_trace() and synth_event_trace_start().
Thanks,
Tom
The following changes since commit 7a1f8097178832627261a16e32973b12a0355dad:
bootconfig: Use parse_args() to find bootconfig and '--' (2020-02-07 20:51:08 -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-fixes-v1
Tom Zanussi (3):
tracing: Add missing nest end to synth_event_trace_start() error case
tracing: Don't return -EINVAL when tracing soft disabled synth events
tracing: Consolidate trace() functions
include/linux/trace_events.h | 2 +-
kernel/trace/trace_events_hist.c | 227 +++++++++++++++------------------------
2 files changed, 87 insertions(+), 142 deletions(-)
--
2.14.1
next reply other threads:[~2020-02-10 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-10 23:06 Tom Zanussi [this message]
2020-02-10 23:06 ` [PATCH 1/3] tracing: Add missing nest end to synth_event_trace_start() error case Tom Zanussi
2020-02-12 3:24 ` Masami Hiramatsu
2020-02-10 23:06 ` [PATCH 2/3] tracing: Don't return -EINVAL when tracing soft disabled synth events Tom Zanussi
2020-02-12 3:24 ` Masami Hiramatsu
2020-02-12 3:28 ` Steven Rostedt
2020-02-12 5:24 ` Masami Hiramatsu
2020-02-10 23:06 ` [PATCH 3/3] tracing: Consolidate trace() functions Tom Zanussi
2020-02-12 3:36 ` 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.1581374549.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.