linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Scordino <claudio@evidence.eu.com>
To: linux-kernel@vger.kernel.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	rmk+kernel@arm.linux.org.uk,
	linux-arm-kernel@lists.arm.linux.org.uk,
	akpm@linux-foundation.org
Subject: [PATCH][RE-SUBMIT] Default setting of the ARM_UNWIND option
Date: Mon, 26 Oct 2009 09:27:47 +0100	[thread overview]
Message-ID: <4AE55D83.7080608@evidence.eu.com> (raw)
In-Reply-To: <1255620333.10164.77.camel@pc1117.cambridge.arm.com>

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

Hi all,

          I didn't get any comment on this patch, so I try to re-submit.

My ARM board hanged at the initial "Calibrating delay loop" message.

After some inspection, I found out the problem to be with commit
adf8b37bafc1495393201a2ae4235846371870d0. This commit introduces stack
unwinding for ARM, and set it enabled by default. However, it seems to
not work with buggy or not-EABI compilers.

My suggestion is to keep the feature (which is fine) but change the
default setting of the option (see the attached patch).

Having this option enabled by default, in fact, means that the kernel
does not boot if the user has a wrong compiler. If so, inspecting the
reason of the hang may require too much time (especially for people not
familiar with this option).

Consider that people may not know that their problem is related to the
ARM_UNWIND option. Therefore, they may waste time bisecting just to
understand where their problem really is.

If we disable this option by default, users who know the real meaning of
the option will still be able of setting it to the proper value.

Any comment ?

Many thanks,

                   Claudio







[-- Attachment #2: 0001-Disable-stack-unwinding-support-by-default-since-it.patch --]
[-- Type: text/x-patch, Size: 1210 bytes --]

From: Claudio Scordino <claudio@evidence.eu.com>
Date: Mon, 19 Oct 2009 11:59:16 +0200
Subject: [PATCH 1/1] Disable stack unwinding support by default, since it does not work on some buggy or not-EABI compilers.

Disable stack unwinding support by default, since it does not work on some
buggy or not-EABI compilers.

Signed-off-by: Claudio Scordino <claudio@evidence.eu.com>
---
 arch/arm/Kconfig.debug |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/arm/Kconfig.debug b/arch/arm/Kconfig.debug
index 1a6f70e..925e3fd 100644
--- a/arch/arm/Kconfig.debug
+++ b/arch/arm/Kconfig.debug
@@ -19,13 +19,13 @@ config FRAME_POINTER
 config ARM_UNWIND
 	bool "Enable stack unwinding support"
 	depends on AEABI && EXPERIMENTAL
-	default y
+	default n
 	help
 	  This option enables stack unwinding support in the kernel
 	  using the information automatically generated by the
 	  compiler. The resulting kernel image is slightly bigger but
 	  the performance is not affected. Currently, this feature
-	  only works with EABI compilers. If unsure say Y.
+	  only works with EABI compilers. If unsure say N.
 
 config DEBUG_USER
 	bool "Verbose user fault messages"
-- 
1.6.0.4









  parent reply	other threads:[~2009-10-26  8:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4AD73DA4.4050006@evidence.eu.com>
     [not found] ` <1255620333.10164.77.camel@pc1117.cambridge.arm.com>
2009-10-19 10:15   ` [PATCH] Default setting of the ARM_UNWIND option Claudio Scordino
2009-10-19 10:16   ` Claudio Scordino
2009-10-26  8:27   ` Claudio Scordino [this message]
2009-10-26 11:10     ` [PATCH][RE-SUBMIT] " Catalin Marinas
2009-10-28 11:37       ` Claudio Scordino
2009-10-28 11:37       ` Claudio Scordino
2009-10-28 14:58         ` Catalin Marinas
2009-10-30 11:11           ` Claudio Scordino
2009-10-30 12:39             ` Catalin Marinas

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=4AE55D83.7080608@evidence.eu.com \
    --to=claudio@evidence.eu.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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;
as well as URLs for NNTP newsgroup(s).