forked from Minki/linux
da6658859b
Commit 2965faa5e0 ("kexec: split kexec_load syscall from kexec core
code") introduced CONFIG_KEXEC_CORE so that CONFIG_KEXEC means whether
the kexec_load system call should be compiled-in and CONFIG_KEXEC_FILE
means whether the kexec_file_load system call should be compiled-in.
These options can be set independently from each other.
Since until now powerpc only supported kexec_load, CONFIG_KEXEC and
CONFIG_KEXEC_CORE were synonyms. That is not the case anymore, so we
need to make a distinction. Almost all places where CONFIG_KEXEC was
being used should be using CONFIG_KEXEC_CORE instead, since
kexec_file_load also needs that code compiled in.
Signed-off-by: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
30 lines
944 B
Makefile
30 lines
944 B
Makefile
ccflags-$(CONFIG_PPC64) := $(NO_MINIMAL_TOC)
|
|
ccflags-$(CONFIG_PPC_PSERIES_DEBUG) += -DDEBUG
|
|
|
|
obj-y := lpar.o hvCall.o nvram.o reconfig.o \
|
|
of_helpers.o \
|
|
setup.o iommu.o event_sources.o ras.o \
|
|
firmware.o power.o dlpar.o mobility.o rng.o \
|
|
pci.o pci_dlpar.o eeh_pseries.o msi.o
|
|
obj-$(CONFIG_SMP) += smp.o
|
|
obj-$(CONFIG_SCANLOG) += scanlog.o
|
|
obj-$(CONFIG_KEXEC_CORE) += kexec.o
|
|
obj-$(CONFIG_PSERIES_ENERGY) += pseries_energy.o
|
|
|
|
obj-$(CONFIG_HOTPLUG_CPU) += hotplug-cpu.o
|
|
obj-$(CONFIG_MEMORY_HOTPLUG) += hotplug-memory.o
|
|
|
|
obj-$(CONFIG_HVC_CONSOLE) += hvconsole.o
|
|
obj-$(CONFIG_HVCS) += hvcserver.o
|
|
obj-$(CONFIG_HCALL_STATS) += hvCall_inst.o
|
|
obj-$(CONFIG_CMM) += cmm.o
|
|
obj-$(CONFIG_DTL) += dtl.o
|
|
obj-$(CONFIG_IO_EVENT_IRQ) += io_event_irq.o
|
|
obj-$(CONFIG_LPARCFG) += lparcfg.o
|
|
obj-$(CONFIG_IBMVIO) += vio.o
|
|
obj-$(CONFIG_IBMEBUS) += ibmebus.o
|
|
|
|
ifeq ($(CONFIG_PPC_PSERIES),y)
|
|
obj-$(CONFIG_SUSPEND) += suspend.o
|
|
endif
|