From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754022AbbDHNJk (ORCPT ); Wed, 8 Apr 2015 09:09:40 -0400 Received: from one.firstfloor.org ([193.170.194.197]:38601 "EHLO one.firstfloor.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753178AbbDHNJN (ORCPT ); Wed, 8 Apr 2015 09:09:13 -0400 From: Andi Kleen To: akpm@linux-foundation.org Cc: linux-kernel@vger.kernel.org, Andi Kleen Subject: [PATCH 1/2] Don't let LATENCYTOP and LOCKDEP select KALLSYMS_ALL Date: Wed, 8 Apr 2015 06:06:44 -0700 Message-Id: <1428498405-7019-1-git-send-email-andi@firstfloor.org> X-Mailer: git-send-email 2.3.3 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Andi Kleen 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 --- 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