From: Andi Kleen <a...@linux.intel.com>
KALLSYMS_ALL enables including data variables into KALLSYMS.
With plain KALLSYMS only functions are included.
LATENCYTOP and LOCKDEP select KALLSYMS_ALL in addition to KALLSYMS.
It's unclear what they actually need _ALL for; they should
only need function backtraces and afaik never touch variables.
LTO currently does not support KALLSYMS_ALL, which prevents
LATENCYTOP and LOCKDEP from working and gives Kconfig errors.
Disable the requirement for KALLSYMS_ALL for them, just use
KALLSYMS.
Signed-off-by: Andi Kleen <a...@linux.intel.com>
---
lib/Kconfig.debug | 2 --
1 file changed, 2 deletions(-)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 3e0289e..062165c 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -1001,7 +1001,6 @@ config LOCKDEP
select STACKTRACE
select FRAME_POINTER if !MIPS && !PPC && !ARM_UNWIND && !S390 &&
!MICROBLAZE && !ARC && !SCORE
select KALLSYMS
- select KALLSYMS_ALL
config LOCK_STAT
bool "Lock usage statistics"
@@ -1469,7 +1468,6 @@ config LATENCYTOP
depends on PROC_FS
select FRAME_POINTER if !MIPS && !PPC && !S390 && !MICROBLAZE &&
!ARM_UNWIND && !ARC
select KALLSYMS
- select KALLSYMS_ALL
select STACKTRACE
select SCHEDSTATS
select SCHED_DEBUG
--
2.3.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
