All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>, Tom Zanussi <zanussi@kernel.org>,
	Masami Hiramatsu <mhiramat@kernel.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Clark Williams <williams@redhat.com>,
	John Kacur <jkacur@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	linux-rt-users@vger.kernel.org,
	linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V5 06/20] trace/osnoise: Allow multiple instances of the same tracer
Date: Tue, 26 Oct 2021 10:38:27 +0200	[thread overview]
Message-ID: <f30262dc-f1cf-4945-5a7d-5ecf5a0b5cc2@kernel.org> (raw)
In-Reply-To: <20211025220856.7fef7581@rorschach.local.home>

On 10/26/21 04:08, Steven Rostedt wrote:
> On Mon, 25 Oct 2021 19:40:31 +0200
> Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
> 
>>  kernel/trace/trace_osnoise.c | 101 +++++++++++++++++++++++++++--------
>>  1 file changed, 78 insertions(+), 23 deletions(-)
>>
>> diff --git a/kernel/trace/trace_osnoise.c b/kernel/trace/trace_osnoise.c
>> index 3db506f49a90..8681ffc3817b 100644
>> --- a/kernel/trace/trace_osnoise.c
>> +++ b/kernel/trace/trace_osnoise.c
>> @@ -64,6 +64,24 @@ static bool osnoise_has_registered_instances(void)
>>  					list);
>>  }
>>  
>> +/*
>> + * osnoise_instance_registered - check if a tr is already registered
>> + */
>> +static int osnoise_instance_registered(struct trace_array *tr)
>> +{
>> +	struct osnoise_instance *inst;
>> +	int found = 0;
>> +
>> +	rcu_read_lock();
>> +	list_for_each_entry_rcu(inst, &osnoise_instances, list) {
>> +		if (inst->tr == tr)
>> +			found = 1;
>> +	}
>> +	rcu_read_unlock();
>> +
>> +	return found;
>> +}
>> +
>>  /*
>>   * osnoise_register_instance - register a new trace instance
>>   *
>> @@ -2048,6 +2066,16 @@ static int osnoise_workload_start(void)
>>  {
>>  	int retval;
>>  
>> +	/*
>> +	 * Instances need to be registered after calling workload
>> +	 * start. Hence, if there is already an instance, the
>> +	 * workload was already registered. Otherwise, this
>> +	 * code is on the way to register the first instance,
>> +	 * and the workload will start.
>> +	 */
>> +	if (osnoise_has_registered_instances())
>> +		return 0;
> 
> Looking at how this is checked before being called, it really should
> return -1, as it is an error if this is called with instances active.

Hum.... maybe my explanation is not good enough. It is not a problem if it is
called with active instances. It would be an error if the same instance was
already registered at this point, but that was checked before. Here it is
checking for other instances that should have enabled the workload.

Does updating the comment with the one below helps?

---- %< ----
Instances need to be registered after calling workload
start. Hence, if there is already a registered instance,
this instance is not the first one to enable the workload,
and a previous instance has already started the workload.

Otherwise, this code is on the way to register the
first instance, and the workload needs to start.
---- >% ----

?


> -- Steve
> 
>> +
>>  	osn_var_reset_all();
>>  
>>  	retval = osnoise_hook_events();
>> @@ -2075,6 +2103,13 @@ static int osnoise_workload_start(void)
>>   */
>>  static void osnoise_workload_stop(void)
>>  {
>> +	/*
>> +	 * Instances need to be unregistered before calling
>> +	 * stop. Hence, if there is a registered instance, more
>> +	 * than one instance is running, and the workload will not
>> +	 * yet stop. Otherwise, this code is on the way to disable
>> +	 * the last instance, and the workload can stop.
>> +	 */
>>  	if (osnoise_has_registered_instances())
>>  		return;
>>  
>> @@ -2096,7 +2131,11 @@ static void osnoise_tracer_start(struct trace_array *tr)
>>  {
>>  	int retval;
>>  
>> -	if (osnoise_has_registered_instances())
>> +	/*
>> +	 * If the instance is already registered, there is no need to
>> +	 * register it again.
>> +	 */
>> +	if (osnoise_instance_registered(tr))
>>  		return;
>>  
>>  	retval = osnoise_workload_start();


  reply	other threads:[~2021-10-26  9:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 17:40 [PATCH V5 00/20] RTLA: An interface for osnoise/timerlat tracers Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 01/20] trace/osnoise: Do not follow tracing_cpumask Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 02/20] trace/osnoise: Improve comments about barrier need for NMI callbacks Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 03/20] trace/osnoise: Split workload start from the tracer start Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 04/20] trace/osnoise: Use start/stop_per_cpu_kthreads() on osnoise_cpus_write() Daniel Bristot de Oliveira
2021-10-26  1:08   ` Steven Rostedt
2021-10-26  8:23     ` Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 05/20] trace/osnoise: Support a list of trace_array *tr Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 06/20] trace/osnoise: Allow multiple instances of the same tracer Daniel Bristot de Oliveira
2021-10-26  2:08   ` Steven Rostedt
2021-10-26  8:38     ` Daniel Bristot de Oliveira [this message]
2021-10-26 13:02       ` Steven Rostedt
2021-10-25 17:40 ` [PATCH V5 07/20] rtla: Real-Time Linux Analysis tool Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 08/20] rtla: Helper functions for rtla Daniel Bristot de Oliveira
2021-10-26 16:22   ` Tao Zhou
2021-10-26 16:26     ` Steven Rostedt
2021-10-26 19:45       ` Daniel Bristot de Oliveira
2021-10-26 19:43     ` Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 09/20] rtla: Add osnoise tool Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 10/20] rtla/osnoise: Add osnoise top mode Daniel Bristot de Oliveira
2021-10-26 16:32   ` Tao Zhou
2021-10-26 19:50     ` Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 11/20] rtla/osnoise: Add the hist mode Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 12/20] rtla: Add timerlat tool and timelart top mode Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 13/20] rtla/timerlat: Add timerlat hist mode Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 14/20] rtla: Add Documentation Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 15/20] rtla: Add rtla osnoise man page Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 16/20] rtla: Add rtla osnoise top documentation Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 17/20] rtla: Add rtla osnoise hist documentation Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 18/20] rtla: Add rtla timerlat documentation Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 19/20] rtla: Add rtla timerlat top documentation Daniel Bristot de Oliveira
2021-10-25 17:40 ` [PATCH V5 20/20] rtla: Add rtla timerlat hist documentation Daniel Bristot de Oliveira

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=f30262dc-f1cf-4945-5a7d-5ecf5a0b5cc2@kernel.org \
    --to=bristot@kernel.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=williams@redhat.com \
    --cc=zanussi@kernel.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.