linux-kernel - Re: [PATCH v0 1/5] x86_64: march=native support

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]

Message-ID: <5edaedc3-17e4-2aff-2cda-f00351e1498c@zytor.com>
Date:   Thu, 7 Dec 2017 15:32:38 -0800
From:   "H. Peter Anvin" <hpa@...or.com>
To:     Alexey Dobriyan <adobriyan@...il.com>, linux-kernel@...r.kernel.org
Cc:     x86@...nel.org, tglx@...utronix.de, mingo@...hat.com
Subject: Re: [PATCH v0 1/5] x86_64: march=native support

One more thing: you HAVE to make
arch/x86/include/asm/required-features.h aware of any features that the
kernel unconditionally depend on.

Again, using the gcc cpp macros that reflect what bits gcc itself
broadcast.  However, this is perhaps where CONFIG flags become
important, since required-features.h has to be able to be compiled in
the bootcode environment, which is different from the normal kernel
compiler environment.

We could, however, automagically generate a reflection of these as a
header file:

	echo '#ifndef __LINUX_CC_DEFINES__'
	echo '#define __LINUX_CC_DEFINES__'
	$(CC) $(c_flags) -x c -E -Wp,-dM /dev/null | sort | \
	sed -nr -e 's/^#define __([^[:space]]+)__$/#define __KERNEL_CC_\1/p'
	echo '#endif

	-hpa