public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Expect a ~15% average slowdown if you use an Intel processor
Date: Fri, 5 Jan 2018 12:31:52 +1100	[thread overview]
Message-ID: <CAC=wYCHeLe-2EcqyGSQke7rpgiSpLcCONp0Z3uLzcTkJBzyADw@mail.gmail.com> (raw)
In-Reply-To: <CAGfcS_n4gQ4w82t8+kVtG+i1t7MjYwkr-hDv46HC5yPXd-kM0A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 975 bytes --]

>
> The settings relevant to Spectre are:
> CONFIG_BPF_JIT - this being set to y is enough to make Intel
> processors vulnerable to variant 1/2.  This being set to y is
> necessary, but not sufficient, for making AMD vulnerable to variant 1.
> net.core.bpf_jit_enable - this being set to 1 along with the config
> option being set is sufficient to make AMD vulnerable to variant 1.
> This setting has no effect on making Intel vulnerable to variant 1 or
> 2.  I suspect this sysctl item won't appear unless it is loaded into
> the kernel in the first place.


Thanks for the clarification. I checked my three systemd systems and all
are;
# CONFIG_BPF_JIT is not set

systemd ebuild is looking for;
$ grep -i bpf /usr/portage/sys-apps/systemd/systemd-2*
/usr/portage/sys-apps/systemd/systemd-235-r1.ebuild:        kernel_is -ge 4
10 && CONFIG_CHECK+=" ~CGROUP_BPF"
/usr/portage/sys-apps/systemd/systemd-236-r4.ebuild:        kernel_is -ge 4
10 && CONFIG_CHECK+=" ~CGROUP_BPF"

[-- Attachment #2: Type: text/html, Size: 1396 bytes --]

  reply	other threads:[~2018-01-05  1:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  3:15 [gentoo-user] Expect a ~15% average slowdown if you use an Intel processor P Levine
2018-01-04  3:25 ` Adam Carter
2018-01-04  3:34   ` Adam Carter
2018-01-04 13:44     ` Corbin Bird
2018-01-04 14:17       ` Rich Freeman
2018-01-04 15:21         ` Corbin Bird
2018-01-04 15:44         ` R0b0t1
2018-01-04 15:46           ` R0b0t1
2018-01-04 16:18           ` Rich Freeman
2018-01-04 21:39             ` [gentoo-user] " Nikos Chantziaras
2018-01-04 21:40               ` Nikos Chantziaras
2018-01-05  0:51               ` Adam Carter
2018-01-05  1:18                 ` Rich Freeman
2018-01-05  1:31                   ` Adam Carter [this message]
2018-01-05 11:10                   ` Peter Humphrey
2018-01-05 18:04                     ` Ian Zimmerman
2018-01-05 19:21                       ` Peter Humphrey
2018-01-06  0:26                         ` Adam Carter
2018-01-06  0:40                           ` Rich Freeman
2018-01-06 13:58                           ` Walter Dnes
2018-01-06 14:12                             ` Rich Freeman
2018-01-05  2:22             ` [gentoo-user] " R0b0t1
2018-01-05  2:31               ` Rich Freeman
2018-01-05  1:52     ` Jalus Bilieyich
2018-01-05  2:16       ` Rich Freeman
2018-01-05 10:28         ` Joerg Schilling

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='CAC=wYCHeLe-2EcqyGSQke7rpgiSpLcCONp0Z3uLzcTkJBzyADw@mail.gmail.com' \
    --to=adamcarter3@gmail.com \
    --cc=gentoo-user@lists.gentoo.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