All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: masami.hiramatsu.pt@hitachi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] tracing/triggers: A couple minor variable name changes
Date: Tue, 07 Jan 2014 11:30:01 -0600	[thread overview]
Message-ID: <1389115801.3040.105.camel@empanada> (raw)
In-Reply-To: <20140106223124.0e5fd0b4@gandalf.local.home>

On Mon, 2014-01-06 at 22:31 -0500, Steven Rostedt wrote:
> On Mon, 06 Jan 2014 20:51:09 -0600
> Tom Zanussi <tom.zanussi@linux.intel.com> wrote:
> 
> > I'll run the next version through my 'testsuite', which unfortunately is
> > still manual (one of the many things on my todo list is automate it)..
> 
> I have some basic tests, attached is one. Which failed. Here's the
> patch that fixes it:
> 
> -- Steve
> 
> tracing: Fix counter for traceon/off event triggers
> 
> The counters for the traceon and traceoff are only suppose to decrement
> when the trigger enables or disables tracing. It is not suppose to decrement
> every time the event is hit.
> 
> Only decrement the counter if the trigger actually did something.
> 
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>

Acked-by: Tom Zanussi <tom.zanussi@linux.intel.com>

> ---
>  kernel/trace/trace_events_trigger.c | 10 ++++++++--
>  1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/trace_events_trigger.c b/kernel/trace/trace_events_trigger.c
> index f6dd115..a53e0da 100644
> --- a/kernel/trace/trace_events_trigger.c
> +++ b/kernel/trace/trace_events_trigger.c
> @@ -742,13 +742,16 @@ traceon_trigger(struct event_trigger_data *data)
>  static void
>  traceon_count_trigger(struct event_trigger_data *data)
>  {
> +	if (tracing_is_on())
> +		return;
> +
>  	if (!data->count)
>  		return;
>  
>  	if (data->count != -1)
>  		(data->count)--;
>  
> -	traceon_trigger(data);
> +	tracing_on();
>  }
>  
>  static void
> @@ -763,13 +766,16 @@ traceoff_trigger(struct event_trigger_data *data)
>  static void
>  traceoff_count_trigger(struct event_trigger_data *data)
>  {
> +	if (!tracing_is_on())
> +		return;
> +
>  	if (!data->count)
>  		return;
>  
>  	if (data->count != -1)
>  		(data->count)--;
>  
> -	traceoff_trigger(data);
> +	tracing_off();
>  }
>  
>  static int



      reply	other threads:[~2014-01-07 17:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-06 19:44 [PATCH 0/2] tracing/triggers: A couple minor variable name changes Tom Zanussi
2014-01-06 19:44 ` [PATCH 1/2 v2] tracing/kprobes: Add trace event trigger invocations Tom Zanussi
2014-01-06 21:56   ` Masami Hiramatsu
2014-01-06 19:44 ` [PATCH 2/2] tracing: Remove double-underscore naming in syscall " Tom Zanussi
2014-01-06 21:13 ` [PATCH 0/2] tracing/triggers: A couple minor variable name changes Steven Rostedt
2014-01-07  0:47   ` Tom Zanussi
2014-01-07  1:50     ` Steven Rostedt
2014-01-07  2:51       ` Tom Zanussi
2014-01-07  3:27         ` Steven Rostedt
2014-01-07 17:29           ` Tom Zanussi
2014-01-07 17:56             ` Steven Rostedt
2014-01-07  3:31         ` Steven Rostedt
2014-01-07 17:30           ` Tom Zanussi [this message]

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=1389115801.3040.105.camel@empanada \
    --to=tom.zanussi@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --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.