From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751633AbdJVO7b convert rfc822-to-8bit (ORCPT ); Sun, 22 Oct 2017 10:59:31 -0400 Received: from mx2.suse.de ([195.135.220.15]:57859 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751259AbdJVO7a (ORCPT ); Sun, 22 Oct 2017 10:59:30 -0400 Date: Sun, 22 Oct 2017 16:01:38 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <20171022130429.GA3165@worktop.lehotels.local> References: <20171022104731.28249-1-bp@alien8.de> <20171022130429.GA3165@worktop.lehotels.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: [tip:x86/urgent] x86/cpu/AMD: Apply the Erratum 688 fix when the BIOS doesn't To: Peter Zijlstra , hpa@zytor.com, torvalds@linux-foundation.org, tglx@linutronix.de, mingo@kernel.org, Yazen.Ghannam@amd.com, mirh@protonmail.ch, sherry.hurwitz@amd.com, stable@vger.kernel.org, linux-kernel@vger.kernel.org CC: linux-tip-commits@vger.kernel.org From: Boris Petkov Message-ID: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On October 22, 2017 3:04:29 PM GMT+02:00, Peter Zijlstra wrote: >I realize this is an erratum work around, but would it be too much to >ask for a small comment explaining the magic values? Revision guide doesn't state what those bits are. By the looks of it, they could be some sort of chicken bits turning off something. >Except for all CPUs that were not online at this point in time... So >suppose I boot with a limited number of CPUs and then later bring up >the >rest, bad things happen. Well, those are small laptops and they're 1 or 2 CPUs tops and you really really really have to try to shoot yourself in the foot... -- Sent from a small device: formatting sux and brevity is inevitable.