[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50CCF6F6.4020107@zytor.com>
Date: Sat, 15 Dec 2012 14:17:26 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: "H. Peter Anvin" <hpa@...ux.intel.com>,
Borislav Petkov <bp@...en8.de>,
"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/15/2012 02:13 PM, Yinghai Lu wrote:
>
> AMD system could have all mem between TOLM and TOHM all WB, and don
> need to set them in MTRRs entries.
>
I include the TOM2 mechanism in the overall umbrella of MTRRs for this
purpose.
> and also your switchover change that handle cross 1G, and 512g, and it
> is not 1G aligned.
> for example, if kernel at 4095G+512M, it will map from 4095G+512M to
> 4096G + 512M.
That is for the kernel region itself (that code is actually unchanged
from the current code), and yes, we could cap that one to _end if there
are systems which have bugs in that area. The dynamic page tables map
1G aligned at a time.
-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