From: Russell King <rmk@arm.linux.org.uk>
To: Tzu-Jung Lee <roylee17@gmail.com>
Cc: linux-kernel@vger.kernel.org, Tzu-Jung Lee <tjlee@ambarella.com>
Subject: Re: [PATCH] ARM: tlb: Compile out MULTI_TLB specific code when MULTI_TLB is undefined
Date: Sat, 17 Sep 2011 09:58:18 +0100 [thread overview]
Message-ID: <20110917085818.GA9262@flint.arm.linux.org.uk> (raw)
In-Reply-To: <CAEvN+1ihRxe4g2wVErEWtg-VSw9dEL5R7YkufdGst5dEyzN8eQ@mail.gmail.com>
On Sat, Sep 17, 2011 at 11:19:02AM +0800, Tzu-Jung Lee wrote:
> Indeed, this is only one of the places where we used to particularly
> build with higher optimization level. More than often, we only disable
> the optimization for interested object files with CFLAGS_foo.o += -g
> -O0. While porting kernel to different platforms, however, failures at
> the early booting stage usually makes low level
> initialization(mm/tlb/cache/cpu...) become the objects that we want to
> disable the optimization for the ease of diagnostic with source level
> debugger. In this cases, patches to the source code become required to
> get the -O0 work for them. Would you consider to have these patches
> merged if they doesn't have side effect.
We've gone some 17 or so years without needing -O0 to debug the kernel.
Why has it now become necessary?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
prev parent reply other threads:[~2011-09-17 8:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 16:31 [PATCH] ARM: tlb: Compile out MULTI_TLB specific code when MULTI_TLB is undefined Tzu-Jung Lee
2011-09-16 20:00 ` Russell King
2011-09-17 3:19 ` Tzu-Jung Lee
2011-09-17 8:58 ` Russell King [this message]
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=20110917085818.GA9262@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=roylee17@gmail.com \
--cc=tjlee@ambarella.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.