Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update ucode on Intel's CPU
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update ucode on Intel's CPU
- From: Yinghai Lu <yinghai@xxxxxxxxxx>
- Date: Fri, 14 Dec 2012 12:08:50 -0800
- Cc: Borislav Petkov <bp@xxxxxxxxx>, "Yu, Fenghua" <fenghua.yu@xxxxxxxxx>, "mingo@xxxxxxxxxx" <mingo@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "tglx@xxxxxxxxxxxxx" <tglx@xxxxxxxxxxxxx>, "hpa@xxxxxxxxxxxxxxx" <hpa@xxxxxxxxxxxxxxx>, "linux-tip-commits@xxxxxxxxxxxxxxx" <linux-tip-commits@xxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
- In-reply-to: <CAE9FiQWRzmG7b+fzwzJKmK4Wjp3dkvu=07Q6mT97og4wsexeSA@mail.gmail.com>
On Fri, Dec 14, 2012 at 12:04 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> On Fri, Dec 14, 2012 at 11:46 AM, H. Peter Anvin <hpa@xxxxxxxxx> wrote:
>>
>> I suspect we don't need init_level4_pgt at all and should just plan to
>> get rid of it. Is there any reason we can't just build the proper
>> kernel page table set in pagetable_init() and switch to it there?
>
> then how to pass the info to AP?
also we should merge early_level4_pgt with init_level4_pgt.
and #PE handler could just extend to use BRK ...
but need to make sure BRK get mapped at first, and BRK could cross the
1G, 512G boundary ...
that could make things less impact to all.
--
To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]
