From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751399Ab2LTCia (ORCPT ); Wed, 19 Dec 2012 21:38:30 -0500 Received: from terminus.zytor.com ([198.137.202.10]:49217 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751397Ab2LTCiX (ORCPT ); Wed, 19 Dec 2012 21:38:23 -0500 Message-ID: <50D279F9.4000707@zytor.com> Date: Wed, 19 Dec 2012 18:37:45 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Jacob Shin CC: Borislav Petkov , Yinghai Lu , "H. Peter Anvin" , "Yu, Fenghua" , "mingo@kernel.org" , "linux-kernel@vger.kernel.org" , "tglx@linutronix.de" , "linux-tip-commits@vger.kernel.org" , Konrad Rzeszutek Wilk , Stefano Stabellini Subject: Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update ucode on Intel's CPU References: <50CD04F1.8020902@zytor.com> <0dcbce7a-d2ae-44fa-9658-81590f71ec47@email.android.com> <20121219220504.GA32212@jshin-Toonie> <50D23EE8.7030904@zytor.com> <20121219225155.GK24895@liondog.tnic> <20121219225941.GB2968@jshin-Toonie> <50D25AA9.3090306@zytor.com> <20121220002954.GA10405@jshin-Toonie> In-Reply-To: <20121220002954.GA10405@jshin-Toonie> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/19/2012 04:29 PM, Jacob Shin wrote: > On Wed, Dec 19, 2012 at 04:24:09PM -0800, H. Peter Anvin wrote: >> 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)? > > Yes, MCE every time and it was fatal. > OK, one more question... there is something odd with the memory ranges here: BIOS-e820: [mem 0x0000000100000000-0x000000e037ffffff] usable BIOS-e820: [mem 0x000000e038000000-0x000000fcffffffff] reserved BIOS-e820: [mem 0x0000010000000000-0x0000011ffeffffff] usable The first usable range here is 4G to 896G + 896M which is an awfully strange number. Similarly, the second range is 1T to 1T + 128G - 16M. The little fiddly bits imply that there is either overshoot of some sort going on -- possibly reserved memory -- or these are fairly arbitrary sizes that don't match any physical bank sizes in which case it should be possible to shuffle it differently... -hpa