From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id EE7F51382C5 for ; Thu, 4 Jan 2018 03:25:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 92C26E087B; Thu, 4 Jan 2018 03:25:06 +0000 (UTC) Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3B4F3E085E for ; Thu, 4 Jan 2018 03:25:06 +0000 (UTC) Received: by mail-ot0-x22b.google.com with SMTP id v40so317115ote.13 for ; Wed, 03 Jan 2018 19:25:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=tw9FW89g/3LRTKGLE2RdesZQK1dU1urosrrWUIs1qVU=; b=m2DIdazeHcXM6VAR9MzjKk0HNWnI0/M0OpLaUSt2k/z/8JPzbPxDvFAB9Rrs7rJ9Wv f1RZzvYY9lJB7PpR/Yh3eQAOKBlWDfNWuGhhiCL38dg+eXTl2LCxdZgz1/vr5DqgbgLJ gxGZVFJbcySpMcsWtRAXrNKGynC05DPFrm5rbPFyPsVILESjLShhoAxRrPiuVQs0dKzX 3WxB70QttrjnMYsGPy2qae5qnLviggPDvvxfyQBIn2aWZlv0s3/7xsKB5x1qpKW21/6b +gbD0ofpz9bqX2dyZ4T6GO2oCuljePtRz6Y+hZxI+78wbDmL8FcRn2IqcxbAo4ZGNdV7 zMrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=tw9FW89g/3LRTKGLE2RdesZQK1dU1urosrrWUIs1qVU=; b=rzu+KYDbl7BwGqWlNgVpZwiGqv+d2f9KxetqvWzprehzreSDFCSQ3GPiuqjXlySAx2 s4QeuIbEpRU2FaYxyAS/7VeXsQgSGOMjSYLwlDcBDx0VkAQzet4lJok3ygsUJui8uQ6T 8aWKAPxogJd1SEJDdROod9OsrqE6E8Sa+BF62RytCSIXoMsHkFMswnoJjJ4wmkjrOyxE ZHyXQ5Kh3rnSOrbK0zTKgA7Ohp5mH3YaXHJPsfb03R0ZpFyy8be2bmiDIYgAtu/LEusD CYdF/2VxolvGGEVLdVwixbUObsWnTUTDYFt6MqTDtZZpuHSC78R3rYCfVtsKO22PBTjy fkfQ== X-Gm-Message-State: AKGB3mKw1D2c41cfP0y0yAPSlqkfGsTuzvw/HyCk+bfM0hhbZ6xFScDI aTu/WWG2ghVBBbsQVdKoBgJ+kzLTHJhyOf8M+2fQS7Jq X-Google-Smtp-Source: ACJfBovsFcuMRUa0ZyOHJF+OCpu9kge8aNNk0bblAcbHLvpSanuzPgiJrL1Z+xj+ND1QYqWQEm25aF9ejeDURDEbKAA= X-Received: by 10.157.61.99 with SMTP id a90mr1968286otc.35.1515036304992; Wed, 03 Jan 2018 19:25:04 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.157.19.65 with HTTP; Wed, 3 Jan 2018 19:25:04 -0800 (PST) In-Reply-To: References: From: Adam Carter Date: Thu, 4 Jan 2018 14:25:04 +1100 Message-ID: Subject: Re: [gentoo-user] Expect a ~15% average slowdown if you use an Intel processor To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="001a11c026eac7ee1e0561eae035" X-Archives-Salt: 9d1bf687-ddf5-4d43-a42e-db10ebc739a1 X-Archives-Hash: 7509a5d26ee73150d14444eeee76f3c0 --001a11c026eac7ee1e0561eae035 Content-Type: text/plain; charset="UTF-8" On Thu, Jan 4, 2018 at 2:15 PM, P Levine 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 > > and Meltdown and Spectre . > > Reported at Bug 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 --001a11c026eac7ee1e0561eae035 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On T= hu, Jan 4, 2018 at 2:15 PM, P Levine <plevine457@gmail.com> wrote:
I'm n= ot sure if it's been mentioned here before but there apparently is a bu= g affecting all Intel CPUs manufactured in the last 10 years or so, in whic= h protected kernel memory is leaked to userspace.=C2=A0 It can't be pat= ched in microcode and will lead to some serious overhead to patch in the OS= .=C2=A0 See,=C2=A0Huge Intel CPU = Bug Allegedly Causes Kernel Memory Vulnerability With Up To 30% Performance= Hit In Windows And Linux=C2=A0and=C2=A0Meltdown and Spectre.

Reported at=C2=A0Bug 643360.

Its been mentioned in another thread, but I guess its a bit o= ff topic there.

Project Zero (Google) found it;
<= a href=3D"https://googleprojectzero.blogspot.com.au/2018/01/reading-privile= ged-memory-with-side.html">https://googleprojectzero.blogspot.com.au/2018/0= 1/reading-privileged-memory-with-side.html

Phoronix has done some benchm= arks on the impact of the kernel based workaround ([Kernel] Page Table Isol= ation (PSI) nee Kaiser)
https://www.phoronix.com/scan.php?page=3Darticle&item=3Dlin= ux-more-x86pti&num=3D1





--001a11c026eac7ee1e0561eae035--