From: kernel test robot <lkp@intel.com>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, Jiri Olsa <jolsa@kernel.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [jolsa-perf:tmp 5/5] kernel/trace/trace_irqsoff.c:287:26: error: too few arguments to function 'trace_function'
Date: Wed, 1 Jan 2025 09:31:04 +0800 [thread overview]
Message-ID: <202501010955.ydD2PbdV-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git tmp
head: e2a63411ac4e1b7b36da9f4c2245570d92842d2e
commit: e2a63411ac4e1b7b36da9f4c2245570d92842d2e [5/5] ftrace: Add arguments to function tracer
config: arc-randconfig-002-20250101 (https://download.01.org/0day-ci/archive/20250101/202501010955.ydD2PbdV-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250101/202501010955.ydD2PbdV-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/202501010955.ydD2PbdV-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace_irqsoff.c: In function 'check_critical_timing':
>> kernel/trace/trace_irqsoff.c:287:26: error: too few arguments to function 'trace_function'
287 | #define __trace_function trace_function
| ^~~~~~~~~~~~~~
kernel/trace/trace_irqsoff.c:350:9: note: in expansion of macro '__trace_function'
350 | __trace_function(tr, CALLER_ADDR0, parent_ip, trace_ctx);
| ^~~~~~~~~~~~~~~~
In file included from kernel/trace/trace_irqsoff.c:19:
kernel/trace/trace.h:685:6: note: declared here
685 | void trace_function(struct trace_array *tr,
| ^~~~~~~~~~~~~~
>> kernel/trace/trace_irqsoff.c:287:26: error: too few arguments to function 'trace_function'
287 | #define __trace_function trace_function
| ^~~~~~~~~~~~~~
kernel/trace/trace_irqsoff.c:372:9: note: in expansion of macro '__trace_function'
372 | __trace_function(tr, CALLER_ADDR0, parent_ip, trace_ctx);
| ^~~~~~~~~~~~~~~~
kernel/trace/trace.h:685:6: note: declared here
685 | void trace_function(struct trace_array *tr,
| ^~~~~~~~~~~~~~
kernel/trace/trace_irqsoff.c: In function 'start_critical_timing':
>> kernel/trace/trace_irqsoff.c:287:26: error: too few arguments to function 'trace_function'
287 | #define __trace_function trace_function
| ^~~~~~~~~~~~~~
kernel/trace/trace_irqsoff.c:401:9: note: in expansion of macro '__trace_function'
401 | __trace_function(tr, ip, parent_ip, tracing_gen_ctx());
| ^~~~~~~~~~~~~~~~
kernel/trace/trace.h:685:6: note: declared here
685 | void trace_function(struct trace_array *tr,
| ^~~~~~~~~~~~~~
kernel/trace/trace_irqsoff.c: In function 'stop_critical_timing':
>> kernel/trace/trace_irqsoff.c:287:26: error: too few arguments to function 'trace_function'
287 | #define __trace_function trace_function
| ^~~~~~~~~~~~~~
kernel/trace/trace_irqsoff.c:435:9: note: in expansion of macro '__trace_function'
435 | __trace_function(tr, ip, parent_ip, trace_ctx);
| ^~~~~~~~~~~~~~~~
kernel/trace/trace.h:685:6: note: declared here
685 | void trace_function(struct trace_array *tr,
| ^~~~~~~~~~~~~~
vim +/trace_function +287 kernel/trace/trace_irqsoff.c
62b915f1060996 Jiri Olsa 2010-04-02 285
62b915f1060996 Jiri Olsa 2010-04-02 286 #else
62b915f1060996 Jiri Olsa 2010-04-02 @287 #define __trace_function trace_function
62b915f1060996 Jiri Olsa 2010-04-02 288
:::::: The code at line 287 was first introduced by commit
:::::: 62b915f1060996a8e1f69be50e3b8e9e43b710cb tracing: Add graph output support for irqsoff tracer
:::::: TO: Jiri Olsa <jolsa@redhat.com>
:::::: CC: Steven Rostedt <rostedt@goodmis.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-01 1:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202501010955.ydD2PbdV-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.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 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.