mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2026-04-03 12:05:13 +02:00
[ Upstream commit f22c81bebf ]
The arm64 kernel doesn't boot with annotated branches
(PROFILE_ANNOTATED_BRANCHES) enabled and CONFIG_DEBUG_VIRTUAL together.
Bisecting it, I found that disabling branch profiling in arch/arm64/mm
solved the problem. Narrowing down a bit further, I found that
physaddr.c is the file that needs to have branch profiling disabled to
get the machine to boot.
I suspect that it might invoke some ftrace helper very early in the boot
process and ftrace is still not enabled(!?).
Rather than playing whack-a-mole with individual files, disable branch
profiling for the entire arch/arm64 tree, similar to what x86 already
does in arch/x86/Kbuild.
Cc: stable@vger.kernel.org
Signed-off-by: Breno Leitao <leitao@debian.org>
Acked-by: Mark Rutland <mark.rutland@arm.com>
Signed-off-by: Will Deacon <will@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
14 lines
347 B
Makefile
14 lines
347 B
Makefile
# SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
# Branch profiling isn't noinstr-safe
|
|
subdir-ccflags-$(CONFIG_TRACE_BRANCH_PROFILING) += -DDISABLE_BRANCH_PROFILING
|
|
|
|
obj-y += kernel/ mm/ net/
|
|
obj-$(CONFIG_KVM) += kvm/
|
|
obj-$(CONFIG_XEN) += xen/
|
|
obj-$(subst m,y,$(CONFIG_HYPERV)) += hyperv/
|
|
obj-$(CONFIG_CRYPTO) += crypto/
|
|
|
|
# for cleaning
|
|
subdir- += boot
|