[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQUB_hVqmbOf8C-bRkdQm85x3b=pk-xa2-8ZMZMfSt5s=w@mail.gmail.com>
Date: Wed, 19 Dec 2012 15:48:35 -0800
From: Yinghai Lu <yinghai@...nel.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Borislav Petkov <bp@...en8.de>, Jacob Shin <jacob.shin@....com>,
"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 Wed, Dec 19, 2012 at 3:43 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 12/19/2012 03:40 PM, Yinghai Lu wrote:
>>
>> On Wed, Dec 19, 2012 at 3:22 PM, H. Peter Anvin <hpa@...or.com> wrote:
>>>
>>> The other bit is that building the real kernel page tables iteratively
>>> (ignoring the early page tables here) is safer, since the real page
>>> table builder is fully aware of the memory map. This means any
>>> "spillover" from the early page tables gets minimized to regions where
>>> there are data objects that have to be accessed early. Since Yinghai
>>> already had iterative page table building working, I don't see any
>>> reason to not use that capability.
>>
>>
>> that is v6, right?
>>
>> including that patch
>>
>
> No, that's just a different way to create the early page tables (and it
> doesn't solve anything, quite on the contrary.) I'm talking about the
> strategy for creating the *permanent* page tables
>
i'm confused. permanent one is in tip/x86/mm2 right?
for for-x86-boot:
so you want v7 plus attached patch ? that change to 2M per PF.
Yinghai
Download attachment "fix_hpa_pe_pgt.patch" of type "application/octet-stream" (2697 bytes)
Powered by blists - more mailing lists