From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>
Cc: Juri Lelli <juri.lelli@redhat.com>,
William White <chwhite@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH V2 3/3] tracing/timerlat: Add user-space interface
Date: Thu, 25 May 2023 19:00:41 +0200 [thread overview]
Message-ID: <67720a34-7519-0974-1fe6-7200f1c59ae0@kernel.org> (raw)
In-Reply-To: <a7b2c215c763e95a56fa1258743332b570c81c9d.1684860626.git.bristot@kernel.org>
[...]
>
> +static void check_timerlat_user_migration(pid_t pid, long dest_cpu);
> /*
> * trace_sched_switch - sched:sched_switch trace event handler
> *
> @@ -1196,6 +1199,9 @@ trace_sched_switch_callback(void *data, bool preempt,
> struct osnoise_variables *osn_var = this_cpu_osn_var();
> int workload = test_bit(OSN_WORKLOAD, &osnoise_options);
>
> + if (unlikely(workload && timerlat_enabled()))
> + check_timerlat_user_migration(n->pid, smp_processor_id());
> +
it should be !workload, anyway, I will move this check to a sched_migrate_task
tracepoint because it runs less frequently and...
[...]
the tracepoint also informs the origin CPU, so it can be passed here:
> +
> +static void check_timerlat_user_migration(pid_t pid, long dest_cpu)
> +{
> + struct osnoise_variables *osn_var;
> + long cpu;
> +
and we can avoid this ugly loop.
> + for_each_possible_cpu(cpu) {
> + osn_var = per_cpu_ptr(&per_cpu_osnoise_var, cpu);
> + if (osn_var->pid == pid && dest_cpu != cpu) {
> + per_cpu_ptr(&per_cpu_timerlat_var, cpu)->uthread_migrate = 1;
> + osnoise_taint("timerlat user thread migrate\n");
> + osnoise_stop_tracing();
> + break;
> + }
> + }
Lazy daniel should have had a look first, but at least now I know I also need
to do some ifdeffery.
-- Daniel
prev parent reply other threads:[~2023-05-25 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 17:22 [PATCH V2 0/3] osnoise/timerlat improvements Daniel Bristot de Oliveira
2023-05-23 17:22 ` [PATCH V2 1/3] tracing/osnoise: Switch from PF_NO_SETAFFINITY to migrate_disable Daniel Bristot de Oliveira
2023-05-23 17:22 ` [PATCH V2 2/3] tracing/osnoise: Skip running osnoise if all instances are off Daniel Bristot de Oliveira
2023-05-23 17:22 ` [PATCH V2 3/3] tracing/timerlat: Add user-space interface Daniel Bristot de Oliveira
2023-05-23 20:59 ` kernel test robot
2023-05-24 8:04 ` kernel test robot
2023-05-24 8:04 ` kernel test robot
2023-05-24 12:48 ` kernel test robot
2023-05-25 14:16 ` Daniel Bristot de Oliveira
2023-05-25 17:00 ` 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=67720a34-7519-0974-1fe6-7200f1c59ae0@kernel.org \
--to=bristot@kernel.org \
--cc=chwhite@redhat.com \
--cc=corbet@lwn.net \
--cc=juri.lelli@redhat.com \
--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
all inboxes | Powered by JetHome®