From: Adam Carter <adamcarter3@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Expect a ~15% average slowdown if you use an Intel processor
Date: Thu, 4 Jan 2018 14:25:04 +1100 [thread overview]
Message-ID: <CAC=wYCH+cTYoMrRtQZLeEvWuEoRb_uZcLs=m5twwUdF322GV_Q@mail.gmail.com> (raw)
In-Reply-To: <CADX8ZBLJttMUsScnOk8jVUp_f0SvT_iLebGQmXjWK9gsO=DK8Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Thu, Jan 4, 2018 at 2:15 PM, P Levine <plevine457@gmail.com> wrote:
> I'm not sure if it's been mentioned here before but there apparently is a
> bug affecting all Intel CPUs manufactured in the last 10 years or so, in
> which protected kernel memory is leaked to userspace. It can't be patched
> in microcode and will lead to some serious overhead to patch in the OS.
> See, Huge Intel CPU Bug Allegedly Causes Kernel Memory Vulnerability With
> Up To 30% Performance Hit In Windows And Linux
> <https://hothardware.com/news/intel-cpu-bug-kernel-memory-isolation-linux-windows-macos>
> and Meltdown and Spectre <https://meltdownattack.com/>.
>
> Reported at Bug 643360 <https://bugs.gentoo.org/643360>.
>
Its been mentioned in another thread, but I guess its a bit off topic there.
Project Zero (Google) found it;
https://googleprojectzero.blogspot.com.au/2018/01/reading-privileged-memory-with-side.html
Phoronix has done some benchmarks on the impact of the kernel based
workaround ([Kernel] Page Table Isolation (PSI) nee Kaiser)
https://www.phoronix.com/scan.php?page=article&item=linux-more-x86pti&num=1
[-- Attachment #2: Type: text/html, Size: 2379 bytes --]
next prev parent reply other threads:[~2018-01-04 3:25 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 [this message]
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
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=wYCH+cTYoMrRtQZLeEvWuEoRb_uZcLs=m5twwUdF322GV_Q@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