[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50D25AA9.3090306@zytor.com>
Date: Wed, 19 Dec 2012 16:24:09 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Jacob Shin <jacob.shin@....com>
CC: Borislav Petkov <bp@...en8.de>, 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 04:07 PM, Jacob Shin wrote:
>
> From what I remember, accessing memory around the memory hole (not
> just the HT hole, but e038000000 ~ 10000000000 on our mentioned system
> ) generated prefetches because the memory hole was marked as WB in PAT.
>
> I'll take a look at the system again, try the blanket MTRR covering
> 0xe000000000 ~ 1TB, and talk to our BIOS guys.
>
Yes, but do they all #MC (as opposed to, say, fetching all FFs)?
-hpa
--
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