linux-kernel - Rewriting kernel config after generation

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-next>] [day] [month] [year] [list]

Message-ID: <20111202053342.GA13877@p183.telecom.by>
Date:	Fri, 2 Dec 2011 08:33:42 +0300
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	mmarek@...e.cz, sam@...nborg.org
Cc:	linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Rewriting kernel config after generation

I'm trying to add compiling with -march=native to the kernel.
The problem is that then some config options become discoverable at
the beginning of the compilation. For example,
CONFIG_X86_L1_CACHE_SHIFT=6 can be derived from "--param l1-cache-line-size=64".
I suspect this is no-go, because all the dependency logic must be
duplicated somewhere else (in the march=native script) for the above
to work.

Is there any cleaner way I'm missing?

In theory, such script could even turn off CONFIG_CPU_SUP_AMD
if it detects Intel CPU.

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