From: kernel test robot <lkp@intel.com>
To: "Chang S. Bae" <chang.seok.bae@intel.com>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, x86@kernel.org, tglx@kernel.org,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
peterz@infradead.org, david.kaplan@amd.com,
chang.seok.bae@intel.com
Subject: Re: [PATCH v3 3/9] stop_machine: Introduce stop_machine_nmi_cpuslocked()
Date: Fri, 16 Oct 2026 15:15:18 +0800 [thread overview]
Message-ID: <202610161559.cSgd4JA0-lkp@intel.com> (raw)
In-Reply-To: <20261015211426.49114-4-chang.seok.bae@intel.com>
Hi Chang,
kernel test robot noticed the following build errors:
[auto build test ERROR on 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907]
url: https://github.com/intel-lab-lkp/linux/commits/Chang-S-Bae/stop_machine-Refactor-multi-CPU-stop-glue-code/20261015-211418
base: 24a19b953e2a3d0ea5a8c4951a0ab8f32720c907
patch link: https://lore.kernel.org/r/20261015211426.49114-4-chang.seok.bae%40intel.com
patch subject: [PATCH v3 3/9] stop_machine: Introduce stop_machine_nmi_cpuslocked()
config: i386-randconfig-1013-20261016 (https://download.01.org/0day-ci/archive/20261016/202610161559.cSgd4JA0-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.4.0-5) 12.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261016/202610161559.cSgd4JA0-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/202610161559.cSgd4JA0-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sched/sched.h:63,
from kernel/sched/rq-offsets.c:5:
>> include/linux/stop_machine.h:226:74: error: unknown type name 'conststruct'; did you mean 'const_true'?
226 | stop_machine_nmi_cpulocked(cpu_stop_nmisafe_fn_t nmisafe_fn, void *data, conststruct cpumask *cpus)
| ^~~~~~~~~~~
| const_true
make[3]: *** [scripts/Makefile.build:185: kernel/sched/rq-offsets.s] Error 1 shuffle=3873254352
make[3]: Target 'prepare' not remade because of errors.
make[2]: *** [Makefile:1425: prepare0] Error 2 shuffle=3873254352
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:248: __sub-make] Error 2 shuffle=3873254352
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:248: __sub-make] Error 2 shuffle=3873254352
make: Target 'prepare' not remade because of errors.
vim +226 include/linux/stop_machine.h
200
201 /**
202 * stop_machine_nmi_cpuslocked() - Freeze CPUs and run a function in NMI context
203 *
204 * @nmisafe_fn: The function to run
205 * @data: The data pointer for @nmisafe_fn()
206 * @cpus: The CPUs to run @nmisafe_fn() on (NULL = one unspecified online CPU)
207 *
208 * Description: This stop_machine() variant runs @nmisafe_fn() from NMI context
209 * to prevent preemption by other NMIs. The callback must be built with noinstr.
210 * Other than that, the semantics match stop_machine_cpuslocked().
211 *
212 * Context: Must be called from within a cpus_read_lock() protected region.
213 * Avoid nested calls to cpus_read_lock().
214 *
215 * Return: 0 if all invocations of @nmisafe_fn return zero, -ENOMEM if cpumask
216 * allocation fails, -EINVAL if not initialized yet or any target CPU failed to
217 * receive NMI. Otherwise, the value returned by an arbitrarily chosen member of
218 * the set of calls to @nmisafe_fn that returned non-zero.
219 */
220 int stop_machine_nmi_cpuslocked(cpu_stop_nmisafe_fn_t nmisafe_fn, void *data,
221 const struct cpumask *cpus);
222
223 #else
224 static inline bool stop_machine_nmi_handler(void) { return false; }
225 static inline int
> 226 stop_machine_nmi_cpulocked(cpu_stop_nmisafe_fn_t nmisafe_fn, void *data, conststruct cpumask *cpus)
227 {
228 return 0;
229 }
230 #endif /* CONFIG_STOP_MACHINE_NMI */
231
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-10-16 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 21:14 [PATCH v3 0/9] x86/microcode: Refactor NMI-based rendezvous mechanism to stop-machine Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 1/9] stop_machine: Refactor multi-CPU stop glue code Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 2/9] stop_machine: Add NMI-based execution path Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 3/9] stop_machine: Introduce stop_machine_nmi_cpuslocked() Chang S. Bae
2026-10-16 7:15 ` kernel test robot [this message]
2026-10-16 13:46 ` Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 4/9] x86/apic: Implement self-NMI support Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 5/9] x86/nmi: Support NMI stop-machine handler Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 6/9] x86/microcode: Distinguish NMI control path on stop-machine callback Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 7/9] x86/microcode: Use stop-machine NMI facility Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 8/9] x86/nmi: Simplify offline microcode handler invocation Chang S. Bae
2026-10-15 21:14 ` [PATCH v3 9/9] x86/microcode: Remove microcode_nmi_handler_enable Chang S. Bae
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=202610161559.cSgd4JA0-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=chang.seok.bae@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.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®