From: Leonardo Bras <leobras@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Leonardo Bras <leobras@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Yury Norov <yury.norov@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Nadav Amit <namit@vmware.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
Chen Zhongjin <chenzhongjin@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>
Subject: [RFC PATCH 1/1] smp: Add tracepoints for functions called with smp_call_function*()
Date: Thu, 6 Apr 2023 04:57:18 -0300 [thread overview]
Message-ID: <20230406075718.68672-1-leobras@redhat.com> (raw)
When running RT workloads in isolated CPUs, many cases of deadline misses
are caused by remote CPU requests such as smp_call_function*().
For those cases, having the names of those functions running around the
deadline miss moment could help finding a target for the next improvements.
Add tracepoints for acquiring the funtion name & argument before entry and
after exitting the called function.
Signed-off-by: Leonardo Bras <leobras@redhat.com>
---
include/trace/events/smp.h | 56 ++++++++++++++++++++++++++++++++++++++
kernel/smp.c | 11 ++++++++
2 files changed, 67 insertions(+)
create mode 100644 include/trace/events/smp.h
diff --git a/include/trace/events/smp.h b/include/trace/events/smp.h
new file mode 100644
index 0000000000000..94aae8d71705d
--- /dev/null
+++ b/include/trace/events/smp.h
@@ -0,0 +1,56 @@
+/* SPDX-License-Identifier: GPL-2.0 */
+#undef TRACE_SYSTEM
+#define TRACE_SYSTEM smp
+
+#if !defined(_TRACE_SMP_H) || defined(TRACE_HEADER_MULTI_READ)
+#define _TRACE_SMP_H
+
+#include <linux/tracepoint.h>
+#include <linux/smp.h>
+
+/*
+ * Tracepoints for a function which is called as an effect of smp_call_function.*
+ */
+TRACE_EVENT(smp_call_function_entry,
+
+ TP_PROTO(smp_call_func_t func, void *info),
+
+ TP_ARGS(func, info),
+
+ TP_STRUCT__entry(
+ __field(void *, func)
+ __field(void *, info)
+ ),
+
+ TP_fast_assign(
+ __entry->func = func;
+ __entry->info = info;
+ ),
+
+ TP_printk("function %ps, argument = %p", __entry->func, __entry->info)
+);
+
+
+TRACE_EVENT(smp_call_function_exit,
+
+ TP_PROTO(smp_call_func_t func, void *info),
+
+ TP_ARGS(func, info),
+
+ TP_STRUCT__entry(
+ __field(void *, func)
+ __field(void *, info)
+ ),
+
+ TP_fast_assign(
+ __entry->func = func;
+ __entry->info = info;
+ ),
+
+ TP_printk("function %ps with argument = %p", __entry->func, __entry->info)
+);
+
+#endif /* _TRACE_SMP_H */
+
+/* This part must be outside protection */
+#include <trace/define_trace.h>
diff --git a/kernel/smp.c b/kernel/smp.c
index 06a413987a14a..38d8dec28c39c 100644
--- a/kernel/smp.c
+++ b/kernel/smp.c
@@ -29,6 +29,9 @@
#include "smpboot.h"
#include "sched/smp.h"
+#define CREATE_TRACE_POINTS
+#include <trace/events/smp.h>
+
#define CSD_TYPE(_csd) ((_csd)->node.u_flags & CSD_FLAG_TYPE_MASK)
#ifdef CONFIG_CSD_LOCK_WAIT_DEBUG
@@ -517,7 +520,9 @@ static int generic_exec_single(int cpu, struct __call_single_data *csd)
csd_lock_record(csd);
csd_unlock(csd);
local_irq_save(flags);
+ trace_smp_call_function_entry(func, info);
func(info);
+ trace_smp_call_function_exit(func, info);
csd_lock_record(NULL);
local_irq_restore(flags);
return 0;
@@ -627,7 +632,9 @@ static void __flush_smp_call_function_queue(bool warn_cpu_offline)
}
csd_lock_record(csd);
+ trace_smp_call_function_entry(func, info);
func(info);
+ trace_smp_call_function_exit(func, info);
csd_unlock(csd);
csd_lock_record(NULL);
} else {
@@ -662,7 +669,9 @@ static void __flush_smp_call_function_queue(bool warn_cpu_offline)
csd_lock_record(csd);
csd_unlock(csd);
+ trace_smp_call_function_entry(func, info);
func(info);
+ trace_smp_call_function_exit(func, info);
csd_lock_record(NULL);
} else if (type == CSD_TYPE_IRQ_WORK) {
irq_work_single(csd);
@@ -975,7 +984,9 @@ static void smp_call_function_many_cond(const struct cpumask *mask,
unsigned long flags;
local_irq_save(flags);
+ trace_smp_call_function_entry(func, info);
func(info);
+ trace_smp_call_function_exit(func, info);
local_irq_restore(flags);
}
--
2.40.0
next reply other threads:[~2023-04-06 7:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 7:57 Leonardo Bras [this message]
2023-04-06 8:15 ` [RFC PATCH 1/1] smp: Add tracepoints for functions called with smp_call_function*() Sebastian Andrzej Siewior
2023-04-06 8:42 ` Leonardo Brás
2023-04-06 13:49 ` Steven Rostedt
2023-04-19 4:04 ` Leonardo Brás
2023-04-06 9:55 ` Peter Zijlstra
2023-04-19 3:45 ` Leonardo Brás
2023-05-03 4:23 ` Leonardo Brás
2023-05-03 14:59 ` Peter Zijlstra
2023-05-03 15:53 ` Leonardo Bras Soares Passos
2023-05-04 11:59 ` Valentin Schneider
2023-05-04 13:34 ` Steven Rostedt
2023-05-04 15:01 ` Peter Zijlstra
2023-05-10 20:27 ` Leonardo Brás
2023-05-10 22:18 ` Leonardo Bras Soares Passos
2023-05-10 23:05 ` Leonardo Bras Soares Passos
2023-05-11 8:13 ` Valentin Schneider
2023-05-11 9:25 ` Leonardo Bras Soares Passos
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=20230406075718.68672-1-leobras@redhat.com \
--to=leobras@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=chenzhongjin@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mtosatti@redhat.com \
--cc=namit@vmware.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=yury.norov@gmail.com \
/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).