xref: /linux/kernel/sched/Makefile (revision 68550cbc6129159b7a6434796b721e8b66ee12f6)
1# SPDX-License-Identifier: GPL-2.0
2ifdef CONFIG_FUNCTION_TRACER
3CFLAGS_REMOVE_clock.o = $(CC_FLAGS_FTRACE)
4endif
5
6# The compilers are complaining about unused variables inside an if(0) scope
7# block. This is daft, shut them up.
8ccflags-y += $(call cc-disable-warning, unused-but-set-variable)
9
10# These files are disabled because they produce non-interesting flaky coverage
11# that is not a function of syscall inputs. E.g. involuntary context switches.
12KCOV_INSTRUMENT := n
13
14# There are numerous data races here, however, most of them are due to plain accesses.
15# This would make it even harder for syzbot to find reproducers, because these
16# bugs trigger without specific input. Disable by default, but should re-enable
17# eventually.
18KCSAN_SANITIZE := n
19
20ifneq ($(CONFIG_SCHED_OMIT_FRAME_POINTER),y)
21# According to Alan Modra <alan@linuxcare.com.au>, the -fno-omit-frame-pointer is
22# needed for x86 only.  Why this used to be enabled for all architectures is beyond
23# me.  I suspect most platforms don't need this, but until we know that for sure
24# I turn this off for IA-64 only.  Andreas Schwab says it's also needed on m68k
25# to get a correct value for the wait-channel (WCHAN in ps). --davidm
26CFLAGS_core.o := $(PROFILING) -fno-omit-frame-pointer
27endif
28
29obj-y += core.o loadavg.o clock.o cputime.o
30obj-y += idle.o fair.o rt.o deadline.o
31obj-y += wait.o wait_bit.o swait.o completion.o
32
33obj-$(CONFIG_SMP) += cpupri.o cpudeadline.o topology.o stop_task.o pelt.o
34obj-$(CONFIG_SCHED_AUTOGROUP) += autogroup.o
35obj-$(CONFIG_SCHEDSTATS) += stats.o
36obj-$(CONFIG_SCHED_DEBUG) += debug.o
37obj-$(CONFIG_CGROUP_CPUACCT) += cpuacct.o
38obj-$(CONFIG_CPU_FREQ) += cpufreq.o
39obj-$(CONFIG_CPU_FREQ_GOV_SCHEDUTIL) += cpufreq_schedutil.o
40obj-$(CONFIG_MEMBARRIER) += membarrier.o
41obj-$(CONFIG_CPU_ISOLATION) += isolation.o
42obj-$(CONFIG_PSI) += psi.o
43obj-$(CONFIG_SCHED_CORE) += core_sched.o
44