From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Masami Hiramatsu <mhiramat@kernel.org>
Subject: Re: [PATCH] tracing/osnoise: Fix notify new tracing_max_latency
Date: Wed, 29 Mar 2023 08:31:33 +0200 [thread overview]
Message-ID: <7607caa6-d76b-519b-b798-0603b7ea70cc@kernel.org> (raw)
In-Reply-To: <20230328191613.33ac3f5e@gandalf.local.home>
On 3/29/23 01:16, Steven Rostedt wrote:
> On Fri, 24 Mar 2023 18:51:35 +0100
> Daniel Bristot de Oliveira <bristot@kernel.org> wrote:
>
>> timerlat is not reporting a new tracing_max_latency for the thread
>> latency. Also, the tracer is reporting new max latency on instances
>> where the tracing is off, creating inconsistencies between the max
>> reported values in the trace and in the tracing_max_latency. Thus
>> only report new tracing_max_latency on active tracing instances.
>
> Sounds to me this patch fixes two different bugs. If so, can you please
> break it up into two different patches?
Yeah, I was dubious about sending one or two patches when I sent this one... But
it makes sense making two of them... so I will do.
Thanks!
-- Daniel
> Thanks!
>
> -- Steve
>
>>
>> Fixes: dae181349f1e ("tracing/osnoise: Support a list of trace_array *tr")
>> Cc: Daniel Bristot de Oliveira <bristot@kernel.org>
>> Cc: Steven Rostedt <rostedt@goodmis.org>
>> Cc: Masami Hiramatsu <mhiramat@kernel.org>
>> Signed-off-by: Daniel Bristot de Oliveira <bristot@kernel.org>
>> ---
>> kernel/trace/trace_osnoise.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/trace/trace_osnoise.c b/kernel/trace/trace_osnoise.c
>> index 210e1f168392..2a1b337ac643 100644
>> --- a/kernel/trace/trace_osnoise.c
>> +++ b/kernel/trace/trace_osnoise.c
>> @@ -1296,7 +1296,7 @@ static void notify_new_max_latency(u64 latency)
>> rcu_read_lock();
>> list_for_each_entry_rcu(inst, &osnoise_instances, list) {
>> tr = inst->tr;
>> - if (tr->max_latency < latency) {
>> + if (tracer_tracing_is_on(tr) && tr->max_latency < latency) {
>> tr->max_latency = latency;
>> latency_fsnotify(tr);
>> }
>> @@ -1738,6 +1738,8 @@ static int timerlat_main(void *data)
>>
>> trace_timerlat_sample(&s);
>>
>> + notify_new_max_latency(diff);
>> +
>> timerlat_dump_stack(time_to_us(diff));
>>
>> tlat->tracing_thread = false;
>
prev parent reply other threads:[~2023-03-29 6:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 17:51 [PATCH] tracing/osnoise: Fix notify new tracing_max_latency Daniel Bristot de Oliveira
2023-03-28 23:16 ` Steven Rostedt
2023-03-29 6:31 ` Daniel Bristot de Oliveira [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=7607caa6-d76b-519b-b798-0603b7ea70cc@kernel.org \
--to=bristot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).