Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Feb 2018 20:14:42 -0700
From:      "@lbutlr" <kremels@kreme.com>
To:        Freebsd Questions <freebsd-questions@freebsd.org>
Subject:   Re: Response to Meltdown and Spectre
Message-ID:  <F395799E-2C94-47E9-AA1C-5CB075C50076@kreme.com>
In-Reply-To: <CA%2BtpaK2o1nbY2W2JVRtogN=P2VM9rag_dodK=GtLWgKwNsYZkg@mail.gmail.com>
References:  <CY1PR01MB12472D916F78A638731ECCE68FFB0@CY1PR01MB1247.prod.exchangelabs.com> <23154.11945.856955.523027@jerusalem.litteratus.org> <5A726B60.7040606@gmail.com> <92120E50-19A7-4A44-90DF-505243D77259@kreme.com> <CA%2BtpaK2o1nbY2W2JVRtogN=P2VM9rag_dodK=GtLWgKwNsYZkg@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 1 Feb 2018, at 16:04, Adam Vande More amvandemore@gmail.com> wrote:
> 
> On Thu, Feb 1, 2018 at 3:48 PM, @lbutlr <kremels@kreme.com> wrote:
> 
>> the trouble is that AMD's behavior has been at least as bad as Intel's, if
>> not worse, in regards to Meltdown,
>> 
> 
> Can you explain what provoked this assertion?

First, they violated (not technically, but they made it bloody obvious) the NDA so that the flaw was widely discovered a week early by adding a comment to a meltdown patch that lead every expert int he field straight to the vulnerability: "The AMD microarchitecture does not allow memory references, including speculative references, that access higher privileged data when running in a lesser privileged mode when that access would result in a page fault."

Second, they initially claimed they were would not release any firmware because they were entirely immune, which was untrue.

They were almost immediately proved to be vulnerable to some of the flaws.

Third, while Intel released (and continues to release) detailed technical information, AMD released PR statements.

Honestly, as bad as Intel has looked in the last month, AMD looks worse since they'd behaved like children.

-- 
Don't be afraid to be weak, Don't be too proud to be strong.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F395799E-2C94-47E9-AA1C-5CB075C50076>