[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50C77F86.5010207@zytor.com>
Date: Tue, 11 Dec 2012 10:46:30 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: 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>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
"linux-tip-commits@...r.kernel.org"
<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:x86/microcode] x86/microcode_intel_early.c: Early update
ucode on Intel's CPU
On 12/11/2012 10:42 AM, Yinghai Lu wrote:
>
> now in for-x86-boot:
> http://git.kernel.org/?p=linux/kernel/git/yinghai/linux-yinghai.git;a=commit;h=8e4e093e6d140f1316953437fdde4e826f5cfd98
>
> it adds extra mapping from the whole kernel when kernel is loaded above 1G.
> from round_down(_text, 2M) to round_up(_end -1, 2M).
>
> Do you mean we need to add extra mapping for realmode_data, cmdline,
> ramdisk too? (not include setup_data, and it is accessed via
> early_ioremap later).
Yes, but...
> but if the user memmap to exclude some page, we will still need to
> relocate the ramdisk.
-ENOPARSE
I really need to look at this in more detail. I'm starting to think
this is done completely backwards.
-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