From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: David Woodhouse <dwmw2@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
David Hildenbrand <david@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jon Masters <jcm@redhat.com>, Marcus Meissner <meissner@suse.de>,
Jiri Kosina <jkosina@suse.cz>,
Dominik Brodowski <linux@dominikbrodowski.net>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 6/6] s390: introduce execute-trampolines for branches
Date: Wed, 7 Feb 2018 13:17:19 +0100 [thread overview]
Message-ID: <20180207131719.4aeb316e@mschwideX1> (raw)
In-Reply-To: <1518005275.3677.112.camel@infradead.org>
On Wed, 07 Feb 2018 12:07:55 +0000
David Woodhouse <dwmw2@infradead.org> wrote:
> On Wed, 2018-02-07 at 11:07 +0100, Pavel Machek wrote:
> > This is really unfortunate naming of kernel option.
> >
> > spectre_v2=off sounds like we are turning the "bug" off, but i somehow
> > suspect you are turning the bug _workaround_ off.
>
> That's consistent with what we have on x86.
>
> > > +ifdef CONFIG_EXPOLINE
> > > + ifeq ($(call cc-option-yn,$(CC_FLAGS_MARCH) -mindirect-branch=thunk),y)
> > > + CC_FLAGS_EXPOLINE := -mindirect-branch=thunk
> > > + CC_FLAGS_EXPOLINE += -mfunction-return=thunk
> > > + CC_FLAGS_EXPOLINE += -mindirect-branch-table
> > > + export CC_FLAGS_EXPOLINE
> > > + cflags-y += $(CC_FLAGS_EXPOLINE)
> > > + else
> > > + $(warning "Your gcc lacks the -mindirect-branch= option")
> > > + endif
> > > +endif
>
> That isn't, though. Linus asked us to drop the $(warning) part.
>
> ... and then spent a week building with a non-retpoline compiler and
> not noticing, so he might have changed his mind ;)
I found the warning to have some value, it helps for the case where my
fingers are faster than my brain and I type "make" instead of "smake"
which uses the alternative compiler with the required support.
@Linus: do you want a warning or prefer not to have one ?
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2018-02-07 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 7:00 [PATCH 0/6] s390: improve speculative execution handling v3 Martin Schwidefsky
2018-02-07 7:00 ` [PATCH 1/6] s390: scrub registers on kernel entry and KVM exit Martin Schwidefsky
2018-02-07 7:00 ` [PATCH 2/6] s390: add optimized array_index_mask_nospec Martin Schwidefsky
2018-02-07 7:00 ` [PATCH 3/6] s390/alternative: use a copy of the facility bit mask Martin Schwidefsky
2018-02-07 7:00 ` [PATCH 4/6] s390: add options to change branch prediction behaviour for the kernel Martin Schwidefsky
2018-02-07 10:02 ` Pavel Machek
2018-02-07 11:49 ` Martin Schwidefsky
2018-02-07 7:00 ` [PATCH 5/6] s390: run user space and KVM guests with modified branch prediction Martin Schwidefsky
2018-02-07 7:00 ` [PATCH 6/6] s390: introduce execute-trampolines for branches Martin Schwidefsky
2018-02-07 10:07 ` Pavel Machek
2018-02-07 11:51 ` Martin Schwidefsky
2018-02-07 12:07 ` David Woodhouse
2018-02-07 12:17 ` Martin Schwidefsky [this message]
2018-02-07 12:20 ` David Woodhouse
2018-02-07 17:55 ` Linus Torvalds
2018-02-07 23:44 ` Masahiro Yamada
2018-02-08 0:05 ` Linus Torvalds
2018-02-08 0:57 ` Kees Cook
2018-02-08 17:11 ` Masahiro Yamada
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=20180207131719.4aeb316e@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dwmw2@infradead.org \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jcm@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=meissner@suse.de \
--cc=pavel@ucw.cz \
--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).