From: "H. Peter Anvin" <hpa@zytor.com>
To: Alexey Dobriyan <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Cc: x86@kernel.org, tglx@linutronix.de, mingo@redhat.com
Subject: Re: [PATCH v0 1/5] x86_64: march=native support
Date: Thu, 7 Dec 2017 15:32:38 -0800 [thread overview]
Message-ID: <5edaedc3-17e4-2aff-2cda-f00351e1498c@zytor.com> (raw)
In-Reply-To: <20171207224154.4687-1-adobriyan@gmail.com>
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
next prev parent reply other threads:[~2017-12-07 23:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 22:41 Alexey Dobriyan
2017-12-07 22:41 ` [PATCH 2/5] -march=native: POPCNT support Alexey Dobriyan
2017-12-07 23:07 ` H. Peter Anvin
2017-12-08 10:09 ` Alexey Dobriyan
2017-12-07 22:41 ` [PATCH 3/5] -march=native: REP MOVSB support Alexey Dobriyan
2017-12-07 22:41 ` [PATCH 4/5] -march=native: REP STOSB Alexey Dobriyan
2017-12-08 19:08 ` Andi Kleen
2017-12-07 22:41 ` [PATCH 5/5] -march=native: MOVBE support Alexey Dobriyan
2017-12-07 23:32 ` H. Peter Anvin [this message]
2017-12-08 9:57 ` [PATCH v0 1/5] x86_64: march=native support Alexey Dobriyan
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=5edaedc3-17e4-2aff-2cda-f00351e1498c@zytor.com \
--to=hpa@zytor.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®