[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1328873119-21553-2-git-send-email-jolsa@redhat.com>
Date: Fri, 10 Feb 2012 12:25:15 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: acme@...hat.com, a.p.zijlstra@...llo.nl, mingo@...e.hu,
paulus@...ba.org, cjashfor@...ux.vnet.ibm.com, fweisbec@...il.com
Cc: linux-kernel@...r.kernel.org
Subject: [PATCH 1/5] unwind, kconfig: Adding UNWIND* options
Adding following config options:
CONFIG_UNWIND
- governs wether the unwind code is compiled in
CONFIG_UNWIND_EH_FRAME
- source of unwind data - eh_frame_hdr/eh_frame
CONFIG_UNWIND_DEBUG_FRAME
- source of unwind data - .debug.frame
---
arch/x86/Kconfig.debug | 2 ++
kernel/Kconfig.unwind | 26 ++++++++++++++++++++++++++
2 files changed, 28 insertions(+), 0 deletions(-)
create mode 100644 kernel/Kconfig.unwind
diff --git a/arch/x86/Kconfig.debug b/arch/x86/Kconfig.debug
index e46c214..4705ba1 100644
--- a/arch/x86/Kconfig.debug
+++ b/arch/x86/Kconfig.debug
@@ -299,4 +299,6 @@ config DEBUG_NMI_SELFTEST
If unsure, say N.
+source "kernel/Kconfig.unwind"
+
endmenu
diff --git a/kernel/Kconfig.unwind b/kernel/Kconfig.unwind
new file mode 100644
index 0000000..273dc68
--- /dev/null
+++ b/kernel/Kconfig.unwind
@@ -0,0 +1,26 @@
+
+config UNWIND
+ bool "Use compiler information to display backtrace dump"
+ ---help---
+ Adding code allowing to use compiled debug information
+ for stack unwinding (results in MUCH bigger kernel
+ and many more panics).
+
+choice
+ prompt "Unwind information source"
+ default UNWIND_EH_FRAME
+ depends on UNWIND
+ ---help---
+ source of unwind information
+
+config UNWIND_EH_FRAME
+ bool "exception frame section"
+ ---help---
+ eh_frame section
+
+config UNWIND_DEBUG_FRAME
+ bool "NOT IMPLEMENTED debug frame section"
+ ---help---
+ debug_frame section
+
+endchoice
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists