[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140118110829.GA2071@amd.pavel.ucw.cz>
Date: Sat, 18 Jan 2014 12:08:29 +0100
From: Pavel Machek <pavel@....cz>
To: Borislav Petkov <bp@...en8.de>
Cc: "H. Peter Anvin" <hpa@...or.com>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
X86 ML <x86@...nel.org>, LKML <linux-kernel@...r.kernel.org>,
Kim Naru <kim.naru@....com>,
Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>,
Sherry Hurwitz <sherry.hurwitz@....com>
Subject: Re: [PATCH] x86, CPU, AMD: Add workaround for family 16h, erratum
793
On Sat 2014-01-18 11:42:31, Borislav Petkov wrote:
> On Sat, Jan 18, 2014 at 03:01:55AM +0100, Pavel Machek wrote:
> > I'd say that proposed "your bios has a bug"
>
> You can always unconditionally print "your bios has a bug". Just like
> that. Without even looking.
Yeah, and we have linux-firmware testing toolkits, to discourage buggy
bioses. In this case it is "your bios has rare and dangerous bug, see CVS-1234".
> If you want to add a warning yourself, you can put it in rc.local using
> userspace goodies like msr-tools. With them you can toggle that bit ad
> absurdum - no need for the kernel except msr.ko.
?? By the time userspace is booted, you have overwritten the MSR, and
information, if the BIOS is buggy, was lost.
So linux-firmware testing toolkit actually has no chance to report
this one.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists