From: kernel test robot <lkp@intel.com>
To: Brian Gerst <brgerst@gmail.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 02/11] x86/preempt: Move preempt count to percpu hot section
Date: Sun, 23 Feb 2025 19:31:03 +0800 [thread overview]
Message-ID: <202502231946.RXtsMrTp-lkp@intel.com> (raw)
In-Reply-To: <20250222190623.262689-3-brgerst@gmail.com>
Hi Brian,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on 01157ddc58dc2fe428ec17dd5a18cc13f134639f]
url: https://github.com/intel-lab-lkp/linux/commits/Brian-Gerst/percpu-Introduce-percpu-hot-section/20250223-031046
base: 01157ddc58dc2fe428ec17dd5a18cc13f134639f
patch link: https://lore.kernel.org/r/20250222190623.262689-3-brgerst%40gmail.com
patch subject: [RFC PATCH 02/11] x86/preempt: Move preempt count to percpu hot section
config: i386-buildonly-randconfig-004-20250223 (https://download.01.org/0day-ci/archive/20250223/202502231946.RXtsMrTp-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250223/202502231946.RXtsMrTp-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/202502231946.RXtsMrTp-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/x86/kernel/asm-offsets.c:9:
In file included from include/linux/crypto.h:15:
In file included from include/linux/completion.h:12:
In file included from include/linux/swait.h:7:
In file included from include/linux/spinlock.h:56:
>> include/linux/preempt.h:340:13: warning: declaration of 'struct task_struct' will not be visible outside of this function [-Wvisibility]
340 | struct task_struct *next);
| ^
1 warning generated.
--
In file included from drivers/platform/surface/surface_hotplug.c:16:
In file included from include/linux/acpi.h:13:
In file included from include/linux/resource_ext.h:11:
In file included from include/linux/slab.h:16:
In file included from include/linux/gfp.h:7:
In file included from include/linux/mmzone.h:8:
In file included from include/linux/spinlock.h:56:
>> include/linux/preempt.h:340:13: warning: declaration of 'struct task_struct' will not be visible outside of this function [-Wvisibility]
340 | struct task_struct *next);
| ^
drivers/platform/surface/surface_hotplug.c:79:39: warning: arithmetic between different enumeration types ('enum shps_dsm_fn' and 'enum shps_irq_type') [-Wenum-enum-conversion]
79 | return SHPS_DSM_FN_IRQ_BASE_PRESENCE + type;
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ ~~~~
2 warnings generated.
--
In file included from kernel/sched/core.c:10:
In file included from include/linux/highmem.h:5:
In file included from include/linux/fs.h:6:
In file included from include/linux/wait_bit.h:8:
In file included from include/linux/wait.h:9:
In file included from include/linux/spinlock.h:56:
>> include/linux/preempt.h:340:13: warning: declaration of 'struct task_struct' will not be visible outside of this function [-Wvisibility]
340 | struct task_struct *next);
| ^
kernel/sched/core.c:4958:38: error: incompatible pointer types passing 'struct task_struct *' to parameter of type 'struct task_struct *' [-Werror,-Wincompatible-pointer-types]
4958 | notifier->ops->sched_out(notifier, next);
| ^~~~
1 warning and 1 error generated.
--
In file included from arch/x86/kernel/asm-offsets.c:9:
In file included from include/linux/crypto.h:15:
In file included from include/linux/completion.h:12:
In file included from include/linux/swait.h:7:
In file included from include/linux/spinlock.h:56:
>> include/linux/preempt.h:340:13: warning: declaration of 'struct task_struct' will not be visible outside of this function [-Wvisibility]
340 | struct task_struct *next);
| ^
1 warning generated.
vim +340 include/linux/preempt.h
e107be36efb2a23 Avi Kivity 2007-07-26 322
e107be36efb2a23 Avi Kivity 2007-07-26 323 /**
e107be36efb2a23 Avi Kivity 2007-07-26 324 * preempt_ops - notifiers called when a task is preempted and rescheduled
e107be36efb2a23 Avi Kivity 2007-07-26 325 * @sched_in: we're about to be rescheduled:
e107be36efb2a23 Avi Kivity 2007-07-26 326 * notifier: struct preempt_notifier for the task being scheduled
e107be36efb2a23 Avi Kivity 2007-07-26 327 * cpu: cpu we're scheduled on
e107be36efb2a23 Avi Kivity 2007-07-26 328 * @sched_out: we've just been preempted
e107be36efb2a23 Avi Kivity 2007-07-26 329 * notifier: struct preempt_notifier for the task being preempted
e107be36efb2a23 Avi Kivity 2007-07-26 330 * next: the task that's kicking us out
8592e6486a177a0 Tejun Heo 2009-12-02 331 *
8592e6486a177a0 Tejun Heo 2009-12-02 332 * Please note that sched_in and out are called under different
8592e6486a177a0 Tejun Heo 2009-12-02 333 * contexts. sched_out is called with rq lock held and irq disabled
8592e6486a177a0 Tejun Heo 2009-12-02 334 * while sched_in is called without rq lock and irq enabled. This
8592e6486a177a0 Tejun Heo 2009-12-02 335 * difference is intentional and depended upon by its users.
e107be36efb2a23 Avi Kivity 2007-07-26 336 */
e107be36efb2a23 Avi Kivity 2007-07-26 337 struct preempt_ops {
e107be36efb2a23 Avi Kivity 2007-07-26 338 void (*sched_in)(struct preempt_notifier *notifier, int cpu);
e107be36efb2a23 Avi Kivity 2007-07-26 339 void (*sched_out)(struct preempt_notifier *notifier,
e107be36efb2a23 Avi Kivity 2007-07-26 @340 struct task_struct *next);
e107be36efb2a23 Avi Kivity 2007-07-26 341 };
e107be36efb2a23 Avi Kivity 2007-07-26 342
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-02-23 11:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 19:06 [RFC PATCH 00/11] Add a percpu subsection for hot data Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 01/11] percpu: Introduce percpu hot section Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 02/11] x86/preempt: Move preempt count to " Brian Gerst
2025-02-23 10:05 ` kernel test robot
2025-02-23 10:49 ` kernel test robot
2025-02-23 11:31 ` kernel test robot [this message]
2025-02-22 19:06 ` [RFC PATCH 03/11] x86/smp: Move cpu number " Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 04/11] x86/retbleed: Move call depth " Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 05/11] x86/percpu: Move top_of_stack " Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 06/11] x86/percpu: Move current_task " Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 07/11] x86/softirq: Move softirq_pending " Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 08/11] x86/irq: Move irq stacks " Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 09/11] x86/percpu: Remove pcpu_hot Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 10/11] x86/stackprotector: Move __stack_chk_guard to percpu hot section Brian Gerst
2025-02-22 19:06 ` [RFC PATCH 11/11] x86/smp: Move this_cpu_off " Brian Gerst
2025-02-23 9:36 ` [RFC PATCH 00/11] Add a percpu subsection for hot data Ingo Molnar
2025-02-23 10:20 ` Ard Biesheuvel
2025-02-23 10:30 ` Uros Bizjak
2025-02-23 17:25 ` Brian Gerst
2025-02-23 17:30 ` Ard Biesheuvel
2025-02-23 14:44 ` Brian Gerst
2025-02-23 18:00 ` Linus Torvalds
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=202502231946.RXtsMrTp-lkp@intel.com \
--to=lkp@intel.com \
--cc=brgerst@gmail.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.