From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: tglx@linutronix.de, mhiramat@kernel.org, namhyung@kernel.org,
vedang.patel@intel.com, bigeasy@linutronix.de,
joel.opensrc@gmail.com, joelaf@google.com,
mathieu.desnoyers@efficios.com, baohong.liu@intel.com,
rajvi.jingar@intel.com, julia@ni.com, fengguang.wu@intel.com,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 0/6] tracing: trace event error_log and inter-event bugfixes
Date: Thu, 12 Apr 2018 10:13:15 -0500 [thread overview]
Message-ID: <cover.1523545519.git.tom.zanussi@linux.intel.com> (raw)
Hi Steve,
Here are a few patches that should be applied on top of the
'Inter-event (e.g. latency) support v9' patchset.
The first fixes another problem I noticed when printing flags.
The rest implement the tracing/events/error_log suggested by Masami,
and update the inter-event code to use it (and remove the old hist
file error mechanism).
Thanks,
Tom
The following changes since commit 404bb11b24fb9a592023c077b878d30ad6da4322:
tracing: Enforce passing in filter=NULL to create_filter() (2018-04-11 11:18:42 -0400)
are available in the git repository at:
https://github.com/tzanussi/linux-trace-inter-event.git tzanussi/inter-event-update2
https://github.com/tzanussi/linux-trace-inter-event/tree/tzanussi/inter-event-update2
Tom Zanussi (6):
tracing: Restore proper field flag printing when displaying triggers
tracing: Add trace event error log
tracing: Save the last hist command's associated event name
tracing: Use trace event error_log with hist triggers
tracing: Add field parsing trace event errors for hist triggers
selftests: ftrace: Fix extended error support testcase
kernel/trace/trace.h | 3 +
kernel/trace/trace_events.c | 172 +++++++++++++++++++
kernel/trace/trace_events_hist.c | 188 +++++++++++----------
.../inter-event/trigger-extended-error-support.tc | 2 +-
4 files changed, 274 insertions(+), 91 deletions(-)
--
1.9.3
next reply other threads:[~2018-04-12 15:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 15:13 Tom Zanussi [this message]
2018-04-12 15:13 ` [PATCH 1/6] tracing: Restore proper field flag printing when displaying triggers Tom Zanussi
2018-04-12 15:13 ` [PATCH 2/6] tracing: Add trace event error log Tom Zanussi
2018-04-12 22:20 ` Steven Rostedt
2018-04-12 23:52 ` Tom Zanussi
2018-04-13 13:45 ` Steven Rostedt
2018-04-13 14:24 ` Tom Zanussi
2018-04-13 14:44 ` Steven Rostedt
2018-04-18 9:34 ` Masami Hiramatsu
2018-04-18 13:49 ` Steven Rostedt
2018-04-19 0:40 ` Namhyung Kim
2018-04-19 14:36 ` Steven Rostedt
2018-04-14 6:31 ` Masami Hiramatsu
2018-04-12 15:13 ` [PATCH 3/6] tracing: Save the last hist command's associated event name Tom Zanussi
2018-04-12 15:13 ` [PATCH 4/6] tracing: Use trace event error_log with hist triggers Tom Zanussi
2018-04-12 15:13 ` [PATCH 5/6] tracing: Add field parsing trace event errors for " Tom Zanussi
2018-04-12 15:13 ` [PATCH 6/6] selftests: ftrace: Fix extended error support testcase Tom Zanussi
2019-01-16 3:31 ` [PATCH 0/6] tracing: trace event error_log and inter-event bugfixes Steven Rostedt
2019-01-16 15:42 ` 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=cover.1523545519.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=baohong.liu@intel.com \
--cc=bigeasy@linutronix.de \
--cc=fengguang.wu@intel.com \
--cc=joel.opensrc@gmail.com \
--cc=joelaf@google.com \
--cc=julia@ni.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=namhyung@kernel.org \
--cc=rajvi.jingar@intel.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=vedang.patel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).