linux-kernel - Re: [PATCH] ARM: tlb: Compile out MULTI_TLB specific code when MULTI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20110917085818.GA9262@flint.arm.linux.org.uk>
Date:	Sat, 17 Sep 2011 09:58:18 +0100
From:	Russell King <rmk@....linux.org.uk>
To:	Tzu-Jung Lee <roylee17@...il.com>
Cc:	linux-kernel@...r.kernel.org, Tzu-Jung Lee <tjlee@...arella.com>
Subject: Re: [PATCH] ARM: tlb: Compile out MULTI_TLB specific code when
	MULTI_TLB is undefined

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:
--
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/