1391e43daSPeter Zijlstraifdef CONFIG_FUNCTION_TRACER 2c0a80c0cSHeiko CarstensCFLAGS_REMOVE_clock.o = $(CC_FLAGS_FTRACE) 3391e43daSPeter Zijlstraendif 4391e43daSPeter Zijlstra 55c9a8750SDmitry Vyukov# These files are disabled because they produce non-interesting flaky coverage 65c9a8750SDmitry Vyukov# that is not a function of syscall inputs. E.g. involuntary context switches. 75c9a8750SDmitry VyukovKCOV_INSTRUMENT := n 85c9a8750SDmitry Vyukov 9391e43daSPeter Zijlstraifneq ($(CONFIG_SCHED_OMIT_FRAME_POINTER),y) 10391e43daSPeter Zijlstra# According to Alan Modra <[email protected]>, the -fno-omit-frame-pointer is 11391e43daSPeter Zijlstra# needed for x86 only. Why this used to be enabled for all architectures is beyond 12391e43daSPeter Zijlstra# me. I suspect most platforms don't need this, but until we know that for sure 13391e43daSPeter Zijlstra# I turn this off for IA-64 only. Andreas Schwab says it's also needed on m68k 14391e43daSPeter Zijlstra# to get a correct value for the wait-channel (WCHAN in ps). --davidm 15391e43daSPeter ZijlstraCFLAGS_core.o := $(PROFILING) -fno-omit-frame-pointer 16391e43daSPeter Zijlstraendif 17391e43daSPeter Zijlstra 183289bdb4SPeter Zijlstraobj-y += core.o loadavg.o clock.o cputime.o 19f5832c19SNicolas Pitreobj-y += idle_task.o fair.o rt.o deadline.o 205dd43ce2SIngo Molnarobj-y += wait.o wait_bit.o swait.o completion.o idle.o 21f5832c19SNicolas Pitreobj-$(CONFIG_SMP) += cpupri.o cpudeadline.o topology.o stop_task.o 221051408fSIngo Molnarobj-$(CONFIG_SCHED_AUTOGROUP) += autogroup.o 23391e43daSPeter Zijlstraobj-$(CONFIG_SCHEDSTATS) += stats.o 24391e43daSPeter Zijlstraobj-$(CONFIG_SCHED_DEBUG) += debug.o 252e76c24dSLi Zefanobj-$(CONFIG_CGROUP_CPUACCT) += cpuacct.o 26adaf9fcdSRafael J. Wysockiobj-$(CONFIG_CPU_FREQ) += cpufreq.o 279bdcb44eSRafael J. Wysockiobj-$(CONFIG_CPU_FREQ_GOV_SCHEDUTIL) += cpufreq_schedutil.o 28*22e4ebb9SMathieu Desnoyersobj-$(CONFIG_MEMBARRIER) += membarrier.o 29