From: Alex Vong <alexvong1995@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation]
Date: Mon, 22 Jan 2018 21:18:33 +0800 [thread overview]
Message-ID: <87lggqt4k6.fsf@gmail.com> (raw)
In-Reply-To: <87po648e2n.fsf@netris.org> (Mark H. Weaver's message of "Sat, 20 Jan 2018 15:34:08 -0500")
Hello Mark,
Mark H Weaver <mhw@netris.org> writes:
> Here are two patches that:
>
> * Add gcc-7.3.0-RC-20180117, which includes support for retpoline.
> * Use gcc-7.3 to build linux-libre on x86 systems.
>
> I'm currently running linux-libre-4.14.14 with full retpoline support:
>
> mhw@jojen ~$ cd /sys/devices/system/cpu/vulnerabilities
> mhw@jojen /sys/devices/system/cpu/vulnerabilities$ grep . *
> meltdown:Mitigation: PTI
> spectre_v1:Vulnerable
> spectre_v2:Mitigation: Full generic retpoline
>
> There's also support for retpoline in linux-libre-4.9.77, but none yet
> in earlier kernels.
>
> My question is: should we push these patches to 'master' now, or should
> we wait until gcc-7.3 is released (possibly as soon as January 24)?
>
> Mark
>
>
[...]
I have a question.
Do we plan to eventually build all programs with all retpoline flags
(-mindirect-branch=thunk, -mfunction-return=thunk, -mindirect-branch-register)
enabled?
In particular, do we build gcc itself with these flags? If so, we will
have to add these flags to BOOT_CFLAGS (which I have problem
understanding how to do it).
next prev parent reply other threads:[~2018-01-22 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 20:34 [PATCHES] gnu: linux-libre: Full retpoline support on x86 [spectre mitigation] Mark H Weaver
2018-01-22 6:09 ` Chris Marusich
2018-01-22 20:51 ` Leo Famulari
2018-01-22 13:18 ` Alex Vong [this message]
2018-01-26 11:41 ` Alex Vong
2018-01-23 21:04 ` Leo Famulari
2018-01-27 15:33 ` Ludovic Courtès
2018-01-27 20:01 ` Mark H Weaver
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=87lggqt4k6.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.