From owner-freebsd-current@freebsd.org Thu Jan 4 14:59:56 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 14BE6EBA904 for ; Thu, 4 Jan 2018 14:59:56 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (static-24-113-41-81.wavecable.com [24.113.41.81]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id E99776D353 for ; Thu, 4 Jan 2018 14:59:55 +0000 (UTC) (envelope-from bsd-lists@BSDforge.com) Received: from udns.ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id w04ExuGP035993 for ; Thu, 4 Jan 2018 07:00:02 -0800 (PST) (envelope-from bsd-lists@BSDforge.com) X-Mailer: UDNSMS MIME-Version: 1.0 In-Reply-To: From: "Chris H" Reply-To: bsd-lists@BSDforge.com To: Subject: Re: Intel CPU design flaw - FreeBSD affected? Date: Thu, 04 Jan 2018 07:00:02 -0800 Message-Id: <39abfc53763a4a83142af49e2d56aa59@udns.ultimatedns.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Jan 2018 14:59:56 -0000 On Thu, 4 Jan 2018 15:33:46 +0100 "Stefan Esser" said > Am 04=2E01=2E18 um 12:56 schrieb Darren Reed: > > On 4/01/2018 11:51 AM, Mark Heily wrote: > >> On Jan 2, 2018 19:05, "Warner Losh" wrote: > >> > >> The register article says the specifics are under embargo still=2E That = would > >> make it hard for anybody working with Intel to comment publicly on the= flaw > >> and any mitigations that may be underway=2E It would be unwise to assume= that > >> all the details are out until the embargo lifts=2E > >> > >> > >> Details of the flaws are now published at: > >> > >> https://meltdownattack=2Ecom > >=20 > > The web page has both: meltdown and spectre=2E > > Most people are only talking about meltdown which doesn't hit AMD=2E > > spectre impacts *both* Intel and AMD=2E > >=20 > > SuSE are making available a microcode patch for AMD 17h processors that > > disables branch prediction: > >=20 > > https://lists=2Eopensuse=2Eorg/opensuse-security-announce/2018-01/msg00004=2E= html >=20 > Disabling branch prediction will have a very noticeable effect on executi= on > speed in general (while split page tables only affect programs that perfo= rm > system calls at a high frequency)=2E OUCH! That was the whole point of these; drop cores, and frequency, for hug= e cache lines, and branch prediction=2E You eliminate that branch prediction, a= nd these become near useless=2E :-( Glad I waited, before getting one! >=20 > I have not fully read the Meltdown and Spectre papers, yet, but I do assu= me, > that the attack at the branch prediction tries to counter KASLR, which we= do > not support at all in FreeBSD=2E >=20 > So, I guess, we do not have to bother with disabling of branch prediction= in > FreeBSD for the time being? >=20 > Regards, STefan --Chris