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] [thread-next>] [day] [month] [year] [list]
Date:	Sat, 17 Sep 2011 11:19:02 +0800
From:	Tzu-Jung Lee <roylee17@...il.com>
To:	Russell King <rmk@....linux.org.uk>
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 4:00 AM, Russell King <rmk@....linux.org.uk> wrote:
> On Sat, Sep 17, 2011 at 12:31:06AM +0800, Tzu-Jung Lee wrote:
>> To eliminate the 'undefined cpu_tlb' errors when the kernel is built with -O0
>
> The kernel requires to be built with optimization in many places, and so
> this is an option we don't support.
>
> --
> Russell King
>  Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
>  maintainer of:
>

Hi Russell,

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.

Thanks,
Roy
--
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