From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [PATCH 09/12] tracing: branch: Use trace_tracing_is_on_cpu() instead of "disabled" field
Date: Sat, 3 May 2025 18:10:14 +0800 [thread overview]
Message-ID: <202505031738.buFg2SBt-lkp@intel.com> (raw)
In-Reply-To: <20250502205349.299144667@goodmis.org>
Hi Steven,
kernel test robot noticed the following build errors:
[auto build test ERROR on trace/for-next]
[also build test ERROR on linus/master v6.15-rc4 next-20250502]
[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/Steven-Rostedt/tracing-mmiotrace-Remove-reference-to-unused-per-CPU-data-pointer/20250503-050317
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/20250502205349.299144667%40goodmis.org
patch subject: [PATCH 09/12] tracing: branch: Use trace_tracing_is_on_cpu() instead of "disabled" field
config: arc-randconfig-001-20250503 (https://download.01.org/0day-ci/archive/20250503/202505031738.buFg2SBt-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250503/202505031738.buFg2SBt-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/202505031738.buFg2SBt-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace_branch.c: In function 'probe_likely_condition':
>> kernel/trace/trace_branch.c:56:43: error: implicit declaration of function 'raw_smp_process_id'; did you mean 'raw_smp_processor_id'? [-Wimplicit-function-declaration]
56 | if (!tracer_tracing_is_on_cpu(tr, raw_smp_process_id()))
| ^~~~~~~~~~~~~~~~~~
| raw_smp_processor_id
vim +56 kernel/trace/trace_branch.c
29
30 static void
31 probe_likely_condition(struct ftrace_likely_data *f, int val, int expect)
32 {
33 struct trace_array *tr = branch_tracer;
34 struct trace_buffer *buffer;
35 struct ring_buffer_event *event;
36 struct trace_branch *entry;
37 unsigned long flags;
38 unsigned int trace_ctx;
39 const char *p;
40
41 if (current->trace_recursion & TRACE_BRANCH_BIT)
42 return;
43
44 /*
45 * I would love to save just the ftrace_likely_data pointer, but
46 * this code can also be used by modules. Ugly things can happen
47 * if the module is unloaded, and then we go and read the
48 * pointer. This is slower, but much safer.
49 */
50
51 if (unlikely(!tr))
52 return;
53
54 raw_local_irq_save(flags);
55 current->trace_recursion |= TRACE_BRANCH_BIT;
> 56 if (!tracer_tracing_is_on_cpu(tr, raw_smp_process_id()))
57 goto out;
58
59 trace_ctx = tracing_gen_ctx_flags(flags);
60 buffer = tr->array_buffer.buffer;
61 event = trace_buffer_lock_reserve(buffer, TRACE_BRANCH,
62 sizeof(*entry), trace_ctx);
63 if (!event)
64 goto out;
65
66 entry = ring_buffer_event_data(event);
67
68 /* Strip off the path, only save the file */
69 p = f->data.file + strlen(f->data.file);
70 while (p >= f->data.file && *p != '/')
71 p--;
72 p++;
73
74 strscpy(entry->func, f->data.func);
75 strscpy(entry->file, p);
76 entry->constant = f->constant;
77 entry->line = f->data.line;
78 entry->correct = val == expect;
79
80 trace_buffer_unlock_commit_nostack(buffer, event);
81
82 out:
83 current->trace_recursion &= ~TRACE_BRANCH_BIT;
84 raw_local_irq_restore(flags);
85 }
86
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2025-05-03 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250502205349.299144667@goodmis.org>
2025-05-03 10:10 ` kernel test robot [this message]
2025-05-05 12:11 ` 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=202505031738.buFg2SBt-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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