From: Tom Zanussi <zanussi@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Bristot de Oliveira <bristot@redhat.com>
Subject: Re: [PATCH] tracing: Have traceon and traceoff trigger honor the instance
Date: Fri, 25 Feb 2022 11:00:18 -0600 [thread overview]
Message-ID: <d3004368d5784e3c2a40e3229d3618a88924b11e.camel@kernel.org> (raw)
In-Reply-To: <20220223223837.14f94ec3@rorschach.local.home>
Hi Steve,
On Wed, 2022-02-23 at 22:38 -0500, Steven Rostedt wrote:
> From: "Steven Rostedt (Google)" <rostedt@goodmis.org>
>
> If a trigger is set on an event to disable or enable tracing within
> an
> instance, then tracing should be disabled or enabled in the instance
> and
> not at the top level, which is confusing to users.
>
> Cc: stable@vger.kernel.org
> Fixes: ae63b31e4d0e2 ("tracing: Separate out trace events from global
> variables")
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace_events_trigger.c | 52 +++++++++++++++++++++++++
> ----
> 1 file changed, 46 insertions(+), 6 deletions(-)
>
> diff --git a/kernel/trace/trace_events_trigger.c
> b/kernel/trace/trace_events_trigger.c
> index e0d50c9577f3..efe563140f27 100644
> --- a/kernel/trace/trace_events_trigger.c
> +++ b/kernel/trace/trace_events_trigger.c
> @@ -1295,6 +1295,16 @@ traceon_trigger(struct event_trigger_data
> *data,
> struct trace_buffer *buffer, void *rec,
> struct ring_buffer_event *event)
> {
> + struct trace_event_file *file = data->private_data;
> +
> + if (file) {
> + if (tracer_tracing_is_on(file->tr))
> + return;
> +
> + tracer_tracing_on(file->tr);
> + return;
> + }
> +
> if (tracing_is_on())
> return;
>
> @@ -1306,8 +1316,15 @@ traceon_count_trigger(struct
> event_trigger_data *data,
> struct trace_buffer *buffer, void *rec,
> struct ring_buffer_event *event)
> {
> - if (tracing_is_on())
> - return;
> + struct trace_event_file *file = data->private_data;
> +
> + if (file) {
> + if (tracer_tracing_is_on(file->tr))
> + return;
> + } else {
> + if (tracing_is_on())
> + return;
> + }
>
> if (!data->count)
> return;
> @@ -1315,7 +1332,10 @@ traceon_count_trigger(struct
> event_trigger_data *data,
> if (data->count != -1)
> (data->count)--;
>
> - tracing_on();
> + if (file)
> + tracer_tracing_on(file->tr);
> + else
> + tracing_on();
> }
>
> static void
> @@ -1323,6 +1343,16 @@ traceoff_trigger(struct event_trigger_data
> *data,
> struct trace_buffer *buffer, void *rec,
> struct ring_buffer_event *event)
> {
> + struct trace_event_file *file = data->private_data;
> +
> + if (file) {
> + if (!tracer_tracing_is_on(file->tr))
> + return;
> +
> + tracer_tracing_off(file->tr);
> + return;
> + }
> +
> if (!tracing_is_on())
> return;
>
> @@ -1334,8 +1364,15 @@ traceoff_count_trigger(struct
> event_trigger_data *data,
> struct trace_buffer *buffer, void *rec,
> struct ring_buffer_event *event)
> {
> - if (!tracing_is_on())
> - return;
> + struct trace_event_file *file = data->private_data;
> +
> + if (file) {
> + if (!tracer_tracing_is_on(file->tr))
> + return;
> + } else {
> + if (!tracing_is_on())
> + return;
> + }
>
> if (!data->count)
> return;
> @@ -1343,7 +1380,10 @@ traceoff_count_trigger(struct
> event_trigger_data *data,
> if (data->count != -1)
> (data->count)--;
>
> - tracing_off();
> + if (file)
> + tracer_tracing_off(file->tr);
> + else
> + tracing_off();
> }
>
> static int
Looks good,
Reviewed-by: Tom Zanussi <zanussi@kernel.org>
Thanks,
Tom
next prev parent reply other threads:[~2022-02-25 17:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 3:38 Steven Rostedt
2022-02-24 8:54 ` Daniel Bristot de Oliveira
2022-02-25 17:00 ` Tom Zanussi [this message]
2022-02-25 17:05 ` Steven Rostedt
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=d3004368d5784e3c2a40e3229d3618a88924b11e.camel@kernel.org \
--to=zanussi@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 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®