[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140114203848.GP29865@pd.tnic>
Date: Tue, 14 Jan 2014 21:38:48 +0100
From: Borislav Petkov <bp@...en8.de>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
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>,
Sherry Hurwitz <sherry.hurwitz@....com>
Subject: Re: [PATCH] x86, CPU, AMD: Add workaround for family 16h, erratum 793
On Tue, Jan 14, 2014 at 02:15:08PM -0600, Aravind Gopalakrishnan wrote:
> Scrubbing the RevGuide for Fam16, I found couple more Errata that need
> workarounds:
Before you go and do that, just ask internally whether those workarounds
are being delivered with AGESA instead. We don't want to have a fix in
the kernel for *every* erratum if it can be helped.
We're making an exception for this one because it can freeze the core
just by executing a locked insn which can be done even in userspace.
> @Boris: Could you please create a branch at bp.git with your patch so
> I can base my work on top of it?
For future AMD patches, make sure to almost always use tip master, i.e.
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git#master
to base your work off of.
> Also, I tested this patch against linux.git on a fam16 based machine
> and it works fine.
Thanks, much appreciated. I'll add your Tested-by.
> (I wasn't sure if you had access to a fam16 based box)
Yeah, I don't. So I'm relying on you for future patches :-)
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
--
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