From: Steven Rostedt <rostedt@goodmis.org>
To: Chunyan Zhang <zhang.chunyan@linaro.org>
Cc: mingo@redhat.com, mathieu.poirier@linaro.org,
serge.broslavsky@linaro.org, broonie@kernel.org,
alexander.shishkin@linux.intel.com, zhang.lyra@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v3 2/4] trace: Add an entry for printing trace log to STM
Date: Tue, 7 Jul 2015 11:58:33 -0400 [thread overview]
Message-ID: <20150707115833.7bb1e613@gandalf.local.home> (raw)
In-Reply-To: <c98a5b99ee6fdfa2451afe862c55ee552d692cd0.1436262902.git.zhang.chunyan@linaro.org>
On Tue, 7 Jul 2015 18:10:41 +0800
Chunyan Zhang <zhang.chunyan@linaro.org> wrote:
> output_stm is a link which is used to connect trace event
> logging with STMs, will be used in the upcoming patches.
>
> Signed-off-by: Chunyan Zhang <zhang.chunyan@linaro.org>
> ---
> include/linux/trace_events.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/include/linux/trace_events.h b/include/linux/trace_events.h
> index 1063c85..28dcdff 100644
> --- a/include/linux/trace_events.h
> +++ b/include/linux/trace_events.h
> @@ -14,6 +14,7 @@ struct trace_buffer;
> struct tracer;
> struct dentry;
> struct bpf_prog;
> +struct trace_buffer_stm;
>
> struct trace_print_flags {
> unsigned long mask;
> @@ -293,6 +294,9 @@ struct trace_event_call {
> */
> int flags; /* static flags of different events */
>
> + void (*output_stm)(struct trace_seq *tmp_seq, void *entry,
> + struct trace_buffer_stm *tb);
> +
Shouldn't the above also have a #ifdef CONFIG_STM_TRACE_EVENT
encompassing it? Otherwise we are adding 8 bytes to every trace event.
-- Steve
> #ifdef CONFIG_PERF_EVENTS
> int perf_refcount;
> struct hlist_head __percpu *perf_events;
> @@ -412,6 +416,10 @@ enum event_trigger_type {
> ETT_EVENT_ENABLE = (1 << 3),
> };
>
> +#ifdef CONFIG_STM_TRACE_EVENT
> +extern void stm_trace_event_write(const char *buf, unsigned len);
> +#endif
> +
> extern int filter_match_preds(struct event_filter *filter, void *rec);
>
> extern int filter_check_discard(struct trace_event_file *file, void *rec,
next prev parent reply other threads:[~2015-07-07 15:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 10:10 [RFC PATCH v3 0/4] Integration of trace events with System Trace IP blocks Chunyan Zhang
2015-07-07 10:10 ` [RFC PATCH v3 1/4] STM trace event: Adding generic buffer interface driver Chunyan Zhang
2015-07-08 10:23 ` Alexander Shishkin
2015-07-08 14:15 ` Mathieu Poirier
2015-07-08 12:10 ` Peter Zijlstra
2015-07-08 13:09 ` Alexander Shishkin
2015-07-07 10:10 ` [RFC PATCH v3 2/4] trace: Add an entry for printing trace log to STM Chunyan Zhang
2015-07-07 15:58 ` Steven Rostedt [this message]
2015-07-08 8:06 ` Chunyan Zhang
2015-07-07 10:10 ` [RFC PATCH v3 3/4] trace: Introduce trace log output function for STM Chunyan Zhang
2015-07-17 20:48 ` Steven Rostedt
2015-07-07 10:10 ` [RFC PATCH v3 4/4] trace: Trace log handler for logging into STM blocks Chunyan Zhang
2015-07-08 12:31 ` Peter Zijlstra
2015-07-08 13:06 ` Chunyan Zhang
2015-07-08 13:22 ` Ingo Molnar
2015-07-08 13:19 ` Steven Rostedt
2015-07-10 9:01 ` Chunyan Zhang
2015-07-17 5:59 ` Chunyan Zhang
2015-07-17 21:07 ` Steven Rostedt
2015-07-07 11:12 ` [RFC PATCH v3 0/4] Integration of trace events with System Trace IP blocks Alexander Shishkin
2015-07-08 7:42 ` Chunyan Zhang
2015-07-08 10:11 ` Alexander Shishkin
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=20150707115833.7bb1e613@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mingo@redhat.com \
--cc=serge.broslavsky@linaro.org \
--cc=zhang.chunyan@linaro.org \
--cc=zhang.lyra@gmail.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
all inboxes | Powered by JetHome®