02fce139fd
- Fix VDSO time-related function behavior for systems where we need to fall back to syscalls, but were instead returning bogus results. - A fix to TLB exception handlers for Cavium Octeon systems where they would inadvertently clobber the $1/$at register. - A build fix for bcm63xx configurations. - Switch to using my @kernel.org email address. -----BEGIN PGP SIGNATURE----- iIwEABYIADQWIQRgLjeFAZEXQzy86/s+p5+stXUA3QUCXbTEbhYccGF1bGJ1cnRv bkBrZXJuZWwub3JnAAoJED6nn6y1dQDd+HsBAJ2Zvzlm+CftfNTPbG1SihhyH3s4 edn8VuexsPJp+TjJAP9UZHPQj35tvS5MWYRg0YsNz9HYPTVclYdEsLS9KbSMCw== =YNU+ -----END PGP SIGNATURE----- gpgsig -----BEGIN PGP SIGNATURE----- iIwEABYIADQWIQRgLjeFAZEXQzy86/s+p5+stXUA3QUCXbylbRYccGF1bGJ1cnRv bkBrZXJuZWwub3JnAAoJED6nn6y1dQDd3JkA/2zyRKMikSbQjyr3E2XRnx0HwIUa UjeQvSR0+wofAI0VAP9D3IzB0ugAsGawUSWeYHK5CXBoSrsFNasjxNBT/G1MDA== =duXm -----END PGP SIGNATURE----- Merge tag 'mips_fixes_5.4_3' into mips-next Pull in mips-fixes primarily to gain build fixes in order to allow better testing of mips-next. A few MIPS fixes: - Fix VDSO time-related function behavior for systems where we need to fall back to syscalls, but were instead returning bogus results. - A fix to TLB exception handlers for Cavium Octeon systems where they would inadvertently clobber the $1/$at register. - A build fix for bcm63xx configurations. - Switch to using my @kernel.org email address. Signed-off-by: Paul Burton <paulburton@kernel.org>
60 lines
2.3 KiB
Text
60 lines
2.3 KiB
Text
#
|
|
# Loongson Processors' Support
|
|
#
|
|
|
|
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += -Wa,--trap
|
|
|
|
#
|
|
# Some versions of binutils, not currently mainline as of 2019/02/04, support
|
|
# an -mfix-loongson3-llsc flag which emits a sync prior to each ll instruction
|
|
# to work around a CPU bug (see __SYNC_loongson3_war in asm/sync.h for a
|
|
# description).
|
|
#
|
|
# We disable this in order to prevent the assembler meddling with the
|
|
# instruction that labels refer to, ie. if we label an ll instruction:
|
|
#
|
|
# 1: ll v0, 0(a0)
|
|
#
|
|
# ...then with the assembler fix applied the label may actually point at a sync
|
|
# instruction inserted by the assembler, and if we were using the label in an
|
|
# exception table the table would no longer contain the address of the ll
|
|
# instruction.
|
|
#
|
|
# Avoid this by explicitly disabling that assembler behaviour. If upstream
|
|
# binutils does not merge support for the flag then we can revisit & remove
|
|
# this later - for now it ensures vendor toolchains don't cause problems.
|
|
#
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += $(call as-option,-Wa$(comma)-mno-fix-loongson3-llsc,)
|
|
|
|
#
|
|
# binutils from v2.25 on and gcc starting from v4.9.0 treat -march=loongson3a
|
|
# as MIPS64 R2; older versions as just R1. This leaves the possibility open
|
|
# that GCC might generate R2 code for -march=loongson3a which then is rejected
|
|
# by GAS. The cc-option can't probe for this behaviour so -march=loongson3a
|
|
# can't easily be used safely within the kbuild framework.
|
|
#
|
|
ifeq ($(call cc-ifversion, -ge, 0409, y), y)
|
|
ifeq ($(call ld-ifversion, -ge, 225000000, y), y)
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += \
|
|
$(call cc-option,-march=loongson3a -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64)
|
|
else
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += \
|
|
$(call cc-option,-march=mips64r2,-mips64r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64)
|
|
endif
|
|
else
|
|
cflags-$(CONFIG_CPU_LOONGSON64) += \
|
|
$(call cc-option,-march=mips64r2,-mips64r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64)
|
|
endif
|
|
|
|
# Some -march= flags enable MMI instructions, and GCC complains about that
|
|
# support being enabled alongside -msoft-float. Thus explicitly disable MMI.
|
|
cflags-y += $(call cc-option,-mno-loongson-mmi)
|
|
|
|
#
|
|
# Loongson Machines' Support
|
|
#
|
|
|
|
platform-$(CONFIG_MACH_LOONGSON64) += loongson64/
|
|
cflags-$(CONFIG_MACH_LOONGSON64) += -I$(srctree)/arch/mips/include/asm/mach-loongson64 -mno-branch-likely
|
|
load-$(CONFIG_CPU_LOONGSON64) += 0xffffffff80200000
|