[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50D24F9D.5070802@zytor.com>
Date: Wed, 19 Dec 2012 15:37:01 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Borislav Petkov <bp@...en8.de>, Jacob Shin <jacob.shin@....com>,
Yinghai Lu <yinghai@...nel.org>,
"H. Peter Anvin" <hpa@...ux.intel.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
"mingo@...nel.org" <mingo@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
Stefano Stabellini <Stefano.Stabellini@...citrix.com>
Subject: Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update
ucode on Intel's CPU
On 12/19/2012 03:30 PM, Borislav Petkov wrote:
> On Wed, Dec 19, 2012 at 03:17:59PM -0800, H. Peter Anvin wrote:
>> I presume with "too big" he really means "oddly shaped".
>
> Yeah, that's why it could be enlarged a little in order to adjust it to
> the MTRR scheme. This is what the BKDG says about it:
>
Yes, they should just cap the hole a few megabytes short and put an UC
MTRR at 0xfc00000000. That should happen regardless... this system is
dangerous without it.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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