forked from Minki/linux
577eebeae3
-fstack-protector uses a special per-cpu "stack canary" value. gcc generates special code in each function to test the canary to make sure that the function's stack hasn't been overrun. On x86-64, this is simply an offset of %gs, which is the usual per-cpu base segment register, so setting it up simply requires loading %gs's base as normal. On i386, the stack protector segment is %gs (rather than the usual kernel percpu %fs segment register). This requires setting up the full kernel GDT and then loading %gs accordingly. We also need to make sure %gs is initialized when bringing up secondary cpus too. To keep things consistent, we do the full GDT/segment register setup on both architectures. Because we need to avoid -fstack-protected code before setting up the GDT and because there's no way to disable it on a per-function basis, several files need to have stack-protector inhibited. [ Impact: allow Xen booting with stack-protector enabled ] Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
21 lines
569 B
Makefile
21 lines
569 B
Makefile
ifdef CONFIG_FUNCTION_TRACER
|
|
# Do not profile debug and lowlevel utilities
|
|
CFLAGS_REMOVE_spinlock.o = -pg
|
|
CFLAGS_REMOVE_time.o = -pg
|
|
CFLAGS_REMOVE_irq.o = -pg
|
|
endif
|
|
|
|
# Make sure early boot has no stackprotector
|
|
nostackp := $(call cc-option, -fno-stack-protector)
|
|
CFLAGS_enlighten.o := $(nostackp)
|
|
CFLAGS_mmu.o := $(nostackp)
|
|
|
|
obj-y := enlighten.o setup.o multicalls.o mmu.o irq.o \
|
|
time.o xen-asm.o xen-asm_$(BITS).o \
|
|
grant-table.o suspend.o
|
|
|
|
obj-$(CONFIG_SMP) += smp.o
|
|
obj-$(CONFIG_PARAVIRT_SPINLOCKS)+= spinlock.o
|
|
obj-$(CONFIG_XEN_DEBUG_FS) += debugfs.o
|
|
|