From: David Woodhouse <dwmw2@infradead.org>
To: Daniel Borkmann <daniel@iogearbox.net>, tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org, mliska@suse.cz,
"H . J . Lu" <hjl.tools@gmail.com>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Jesper Dangaard Brouer" <brouer@redhat.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
"Magnus Karlsson" <magnus.karlsson@intel.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] x86, retpolines: entirely disable switch jump tables when retpolines are enabled
Date: Mon, 25 Mar 2019 14:28:51 +0000 [thread overview]
Message-ID: <73ab8319a67a2d894564019c6bb0a806455987c6.camel@infradead.org> (raw)
In-Reply-To: <20190325135620.14882-1-daniel@iogearbox.net>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
On Mon, 2019-03-25 at 14:56 +0100, Daniel Borkmann wrote:
> More than 20 switch cases are not expected to be fast-path critical, but
> it would still be good to align with gcc behavior for versions < 8.4.0 in
> order to have consistency across supported gcc versions. vmlinux size is
> slightly growing by 0.27% for older gcc. This flag is only set to work
> around affected gcc, no change for clang.
I note your final sentence doesn't actually say that clang doesn't have
this problem, and doesn't *need* this (or an equivalent) change.
It should say that (if it's true). And if it isn't true, then other
remedial action would be in order.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5174 bytes --]
next prev parent reply other threads:[~2019-03-25 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 13:56 [PATCH] x86, retpolines: entirely disable switch jump tables when retpolines are enabled Daniel Borkmann
2019-03-25 14:28 ` David Woodhouse [this message]
2019-03-25 14:37 ` Daniel Borkmann
2019-03-25 14:43 ` David Woodhouse
2019-03-28 12:43 ` [tip:x86/urgent] x86/retpolines: Disable " tip-bot for Daniel Borkmann
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=73ab8319a67a2d894564019c6bb0a806455987c6.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hjl.tools@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.karlsson@intel.com \
--cc=mliska@suse.cz \
--cc=tglx@linutronix.de \
--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).