mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: acme@redhat.com, a.p.zijlstra@chello.nl, mingo@elte.hu,
	paulus@samba.org, cjashfor@linux.vnet.ibm.com,
	fweisbec@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 1/5] unwind, kconfig: Adding UNWIND* options
Date: Fri, 10 Feb 2012 12:25:15 +0100	[thread overview]
Message-ID: <1328873119-21553-2-git-send-email-jolsa@redhat.com> (raw)
In-Reply-To: <1328873119-21553-1-git-send-email-jolsa@redhat.com>

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


  reply	other threads:[~2012-02-10 11:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-10 11:25 [RFC 0/5] kernel: backtrace unwind support Jiri Olsa
2012-02-10 11:25 ` Jiri Olsa [this message]
2012-02-10 11:25 ` [PATCH 2/5] unwind, x86: Generate exception frames data for UNWIND_EH_FRAME option Jiri Olsa
2012-02-10 11:25 ` [PATCH 3/5] unwind, dwarf: Add dwarf unwind support Jiri Olsa
2012-02-10 11:25 ` [PATCH 4/5] unwind, api: Add unwind interface and implementation for x86_64 Jiri Olsa
2012-02-10 11:25 ` [PATCH 5/5] unwind, test: Add backtrace unwind test code Jiri Olsa
2012-02-10 17:43 ` [RFC 0/5] kernel: backtrace unwind support Peter Zijlstra
2012-02-10 18:59   ` Linus Torvalds
2012-02-10 19:27     ` Arnaldo Carvalho de Melo
2012-02-10 19:32       ` Linus Torvalds
2012-02-10 19:39         ` Arnaldo Carvalho de Melo
2012-02-10 19:42           ` Arnaldo Carvalho de Melo
2012-02-10 19:44       ` Ingo Molnar
2012-02-10 20:18         ` Jiri Olsa
2012-02-10 20:37           ` Linus Torvalds
2012-02-14  2:22             ` Benjamin Herrenschmidt
2012-02-11 14:38           ` Ingo Molnar
2012-02-11 23:36             ` Jiri Olsa
2012-02-11  3:25         ` Frederic Weisbecker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1328873119-21553-2-git-send-email-jolsa@redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®