From: Pavel Machek <pavel@ucw.cz>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Linux 5.0-ad1: -march=native support
Date: Wed, 27 Mar 2019 16:29:23 +0100 [thread overview]
Message-ID: <20190327152922.GA14937@amd> (raw)
In-Reply-To: <20190304171916.GA1694@avx2>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Mon 2019-03-04 20:19:16, Alexey Dobriyan wrote:
> -ad1 patchset adds support for compiling kernel with "-march=native"
> compiler option optimizing kernel for the specific CPU. "-march=native"
> has been available in userspace for a long time and is trivial to enable
> in Gentoo specifically.
>
> "-march=native" can be used for folks like me who compile kernels on
> their home machines and never share binaries.
>
> See the link for more information:
>
> https://www.shlomifish.org/humour/by-others/funroll-loops/Gentoo-is-Rice.html
>
> Requirements:
>
> Intel CPU
> x86_64 arch
>
> Usage:
>
> # apply -ad1 patchset
>
> # copy regular kernel .config
>
> # enable "-march=native" support in
> # "Processor type and features"
> # "Processor family"
>
> # ensure CONFIG_MARCH_NATIVE is enabled
> $ grep -e CONFIG_MARCH_NATIVE .config
>
> # workaround kbuild race condition if "-j" is used
> $ make syncconfig
Linus is unlikely to take this directly; you may want to Cc X86
MAINTAINERS.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2019-03-27 15:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 17:19 Linux 5.0-ad1: -march=native support Alexey Dobriyan
2019-03-27 15:29 ` Pavel Machek [this message]
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=20190327152922.GA14937@amd \
--to=pavel@ucw.cz \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).