Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751379AbeACTlo convert rfc822-to-8bit (ORCPT + 1 other); Wed, 3 Jan 2018 14:41:44 -0500 Received: from smtp-16.smcloud.com ([198.36.167.16]:30267 "HELO smtp-16.smcloud.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751053AbeACTlm (ORCPT ); Wed, 3 Jan 2018 14:41:42 -0500 X-Greylist: delayed 315 seconds by postgrey-1.27 at vger.kernel.org; Wed, 03 Jan 2018 14:41:42 EST From: "Tim Mouraveiko" Organization: IPCopper, Inc. To: linux-kernel@vger.kernel.org Date: Wed, 03 Jan 2018 11:38:14 -0800 MIME-Version: 1.0 Subject: Re: [PATCH] x86/cpu, x86/pti: Do not enable PTI on AMD processors Message-ID: <5A4D3126.11790.FCAAD77A@tim.ml.ipcopper.com> X-mailer: Pegasus Mail for Windows (4.52) Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Content-description: Mail message body Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On 12/26/2017 09:43 PM, Tom Lendacky wrote: >AMD processors are not subject to the types of attacks that the kernel page table isolation feature protects against. There is no doubt this is a serious flaw. This thread reminded me - about a year ago we discovered a software code that bricked an Intel CPU. The software code was executed and the processor seized. The Motherboard was reset via the reset button, but the processor never came back. It was rather dead - the CPU did not even draw any power. We contacted Intel and one of their personnel suggested that they were aware of it. I never quite understood if it was a processor feature or a flaw. Tim