The patch titled
Subject: lib/Kconfig.debug: don't let LATENCYTOP and LOCKDEP select KALLSYMS_ALL
has been added to the -mm tree. Its filename is
dont-let-latencytop-and-lockdep-select-kallsyms_all.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/dont-let-latencytop-and-lockdep-select-kallsyms_all.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/dont-let-latencytop-and-lockdep-select-kallsyms_all.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Andi Kleen <ak@xxxxxxxxxxxxxxx>
Subject: lib/Kconfig.debug: don't let LATENCYTOP and LOCKDEP select KALLSYMS_ALL
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 <ak@xxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
lib/Kconfig.debug | 2 --
1 file changed, 2 deletions(-)
diff -puN lib/Kconfig.debug~dont-let-latencytop-and-lockdep-select-kallsyms_all lib/Kconfig.debug
--- a/lib/Kconfig.debug~dont-let-latencytop-and-lockdep-select-kallsyms_all
+++ a/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
_
Patches currently in -mm which might be from ak@xxxxxxxxxxxxxxx are
mm-refactor-do_wp_page-extract-the-reuse-case.patch
mm-refactor-do_wp_page-rewrite-the-unlock-flow.patch
mm-refactor-do_wp_page-extract-the-page-copy-flow.patch
mm-refactor-do_wp_page-handling-of-shared-vma-into-a-function.patch
mm-memory-failurec-define-page-types-for-action_result-in-one-place.patch
mm-memory-failurec-define-page-types-for-action_result-in-one-place-v3.patch
dont-let-latencytop-and-lockdep-select-kallsyms_all.patch
test-hexdumpc-fix-initconst-confusion.patch
linux-next.patch
gitignore-ignore-tar.patch
do_shared_fault-check-that-mmap_sem-is-held.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
