From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753155AbaAQWuZ (ORCPT ); Fri, 17 Jan 2014 17:50:25 -0500 Received: from mail.skyhub.de ([78.46.96.112]:40788 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751767AbaAQWuX (ORCPT ); Fri, 17 Jan 2014 17:50:23 -0500 Date: Fri, 17 Jan 2014 23:50:13 +0100 From: Borislav Petkov To: Pavel Machek Cc: "H. Peter Anvin" , Henrique de Moraes Holschuh , X86 ML , LKML , Kim Naru , Aravind Gopalakrishnan , Sherry Hurwitz Subject: Re: [PATCH] x86, CPU, AMD: Add workaround for family 16h, erratum 793 Message-ID: <20140117225013.GE14649@pd.tnic> References: <20140114114133.GA31473@khazad-dum.debian.net> <20140114115547.GA29887@pd.tnic> <52D55468.6000000@zytor.com> <20140114153534.GE29865@pd.tnic> <20140114162722.GF29865@pd.tnic> <20140117222806.GB13930@amd.pavel.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140117222806.GB13930@amd.pavel.ucw.cz> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 17, 2014 at 11:28:06PM +0100, Pavel Machek wrote: > Would it make sense to printk() a warning? No because people come and start bitching about their dmesg containing a warning and whether their hardware is b0rked without even reading the actual words. > BIOS is clearly buggy in this case, and it may cause problems with > another operating system, earlier kernel, or maybe early in boot > before MSR is written... Well, if the problem happens, the machine will lock. If it doesn't lock => no problem and we apply the workaround => no problem at all. :-) -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --