From: kernel test robot <lkp@intel.com>
To: "jempty.liang" <imntjempty@163.com>,
rostedt@goodmis.org, mhiramat@kernel.org, mark.rutland@arm.com,
mathieu.desnoyers@efficios.com
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org,
"jempty.liang" <imntjempty@163.com>
Subject: Re: [PATCH v2] tracing: Fix funcgraph_exit calltime/rettime offset for 32-bit ARM
Date: Tue, 3 Feb 2026 12:06:03 +0800 [thread overview]
Message-ID: <202602031142.uHVfwxw3-lkp@intel.com> (raw)
In-Reply-To: <20260202123342.2544795-1-imntjempty@163.com>
Hi jempty.liang,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trace/for-next]
[also build test WARNING on linus/master v6.19-rc8 next-20260202]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/jempty-liang/tracing-Fix-funcgraph_exit-calltime-rettime-offset-for-32-bit-ARM/20260202-203926
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/20260202123342.2544795-1-imntjempty%40163.com
patch subject: [PATCH v2] tracing: Fix funcgraph_exit calltime/rettime offset for 32-bit ARM
config: x86_64-buildonly-randconfig-004-20260203 (https://download.01.org/0day-ci/archive/20260203/202602031142.uHVfwxw3-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260203/202602031142.uHVfwxw3-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202602031142.uHVfwxw3-lkp@intel.com/
All warnings (new ones prefixed by >>):
kernel/trace/trace_irqsoff.c: In function 'irqsoff_graph_return':
>> kernel/trace/trace_irqsoff.c:224:13: warning: unused variable 'rettime' [-Wunused-variable]
224 | u64 rettime;
| ^~~~~~~
vim +/rettime +224 kernel/trace/trace_irqsoff.c
62b915f1060996 Jiri Olsa 2010-04-02 214
37238abe3cb47b Steven Rostedt (VMware 2024-06-03 215) static void irqsoff_graph_return(struct ftrace_graph_ret *trace,
2ca8c112c9676e Masami Hiramatsu (Google 2024-12-26 216) struct fgraph_ops *gops,
2ca8c112c9676e Masami Hiramatsu (Google 2024-12-26 217) struct ftrace_regs *fregs)
62b915f1060996 Jiri Olsa 2010-04-02 218 {
62b915f1060996 Jiri Olsa 2010-04-02 219 struct trace_array *tr = irqsoff_trace;
62b915f1060996 Jiri Olsa 2010-04-02 220 struct trace_array_cpu *data;
62b915f1060996 Jiri Olsa 2010-04-02 221 unsigned long flags;
36590c50b2d072 Sebastian Andrzej Siewior 2021-01-25 222 unsigned int trace_ctx;
a485ea9e3ef31a Steven Rostedt 2025-01-13 223 u64 *calltime;
66611c04757096 Steven Rostedt 2025-01-21 @224 u64 rettime;
a485ea9e3ef31a Steven Rostedt 2025-01-13 225 int size;
62b915f1060996 Jiri Olsa 2010-04-02 226
12117f3307b63f Steven Rostedt (VMware 2024-06-03 227) ftrace_graph_addr_finish(gops, trace);
5cf99a0f3161bc Steven Rostedt (VMware 2018-11-29 228)
5e6d2b9cfa3a6e Steven Rostedt 2010-10-05 229 if (!func_prolog_dec(tr, &data, &flags))
62b915f1060996 Jiri Olsa 2010-04-02 230 return;
62b915f1060996 Jiri Olsa 2010-04-02 231
77a67833e830fd jempty.liang 2026-02-02 232 trace->rettime = trace_clock_local();
a485ea9e3ef31a Steven Rostedt 2025-01-13 233 calltime = fgraph_retrieve_data(gops->idx, &size);
c834a97962c708 Steven Rostedt 2025-10-08 234 if (calltime) {
77a67833e830fd jempty.liang 2026-02-02 235 trace->calltime = *calltime;
36590c50b2d072 Sebastian Andrzej Siewior 2021-01-25 236 trace_ctx = tracing_gen_ctx_flags(flags);
77a67833e830fd jempty.liang 2026-02-02 237 __trace_graph_return(tr, trace, trace_ctx);
c834a97962c708 Steven Rostedt 2025-10-08 238 }
90633c34c36d0c Steven Rostedt 2025-05-05 239 local_dec(&data->disabled);
62b915f1060996 Jiri Olsa 2010-04-02 240 }
62b915f1060996 Jiri Olsa 2010-04-02 241
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-02-03 4:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 12:33 [PATCH v2] tracing: Fix funcgraph_exit calltime/rettime offset for 32-bit ARM jempty.liang
2026-02-02 15:38 ` Steven Rostedt
2026-02-02 16:08 ` Steven Rostedt
2026-02-03 10:04 ` jempty.liang
2026-02-03 14:30 ` Steven Rostedt
2026-02-03 16:20 ` Steven Rostedt
2026-02-04 1:21 ` jempty.liang
2026-02-03 9:42 ` jempty.liang
2026-02-03 4:06 ` kernel test robot [this message]
2026-02-03 4:26 ` kernel test robot
2026-02-03 5:50 ` kernel test robot
2026-02-03 7:18 ` kernel test robot
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=202602031142.uHVfwxw3-lkp@intel.com \
--to=lkp@intel.com \
--cc=imntjempty@163.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--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