public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing/sysprof: add missing tracing_{start,stop}_record_cmdline()
Date: Tue, 10 Feb 2009 10:54:24 -0200	[thread overview]
Message-ID: <20090210125424.GC12820@ghostprotocols.net> (raw)
In-Reply-To: <4990fdb7.0e0f660a.1d27.5399@mx.google.com>

Em Tue, Feb 10, 2009 at 04:43:30AM +0100, Frederic Weisbecker escreveu:
> Add the missing pair tracing_{start,stop}_record_cmdline() to record well
> the cmdline associated with pid.
> 
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>

This is another thing that I think begs for a TRACE_INIT_CMDLINE in
struct trace->flags so that just before calling ->init we call
tracing_start_cmdline_record? no?

Another thing I noticed is that even we having a ->stop most of the time
this semantic action is done thru ->reset :-\

- Arnaldo

>  kernel/trace/trace_sysprof.c |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/kernel/trace/trace_sysprof.c b/kernel/trace/trace_sysprof.c
> index 84ca9d8..9902c15 100644
> --- a/kernel/trace/trace_sysprof.c
> +++ b/kernel/trace/trace_sysprof.c
> @@ -238,6 +238,8 @@ static int stack_trace_init(struct trace_array *tr)
>  {
>  	sysprof_trace = tr;
>  
> +	tracing_start_cmdline_record();
> +
>  	mutex_lock(&sample_timer_lock);
>  	start_stack_timers();
>  	tracer_enabled = 1;
> @@ -247,6 +249,7 @@ static int stack_trace_init(struct trace_array *tr)
>  
>  static void stack_trace_reset(struct trace_array *tr)
>  {
> +	tracing_stop_cmdline_record();
>  	stop_stack_trace(tr);
>  }

  parent reply	other threads:[~2009-02-10 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  3:43 [PATCH 1/2] tracing/sysprof: add missing tracing_{start,stop}_record_cmdline() Frederic Weisbecker
2009-02-10 12:27 ` Ingo Molnar
2009-02-10 12:31   ` Ingo Molnar
2009-02-10 14:10     ` Frederic Weisbecker
2009-02-10 14:25       ` Ingo Molnar
2009-02-10 14:49         ` Frederic Weisbecker
2009-02-11 12:04           ` Ingo Molnar
2009-02-11 12:10             ` Ingo Molnar
2009-02-11 12:15               ` Ingo Molnar
2009-02-10 14:26       ` Steven Rostedt
2009-02-10 14:39         ` Frederic Weisbecker
2009-02-10 12:54 ` Arnaldo Carvalho de Melo [this message]
2009-02-10 14:26   ` Frederic Weisbecker

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=20090210125424.GC12820@ghostprotocols.net \
    --to=acme@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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