[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130107155339.GA29449@x1.alien8.de>
Date: Mon, 7 Jan 2013 16:53:39 +0100
From: Borislav Petkov <bp@...en8.de>
To: Yinghai Lu <yinghai@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
"H. Peter Anvin" <hpa@...or.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Jan Kiszka <jan.kiszka@....de>,
Jason Wessel <jason.wessel@...driver.com>,
linux-kernel@...r.kernel.org,
Alexander Duyck <alexander.h.duyck@...el.com>,
Fenghua Yu <fenghua.yu@...el.com>
Subject: Re: [PATCH v7u1 05/31] x86, 64bit: copy zero-page early
On Thu, Jan 03, 2013 at 04:48:25PM -0800, Yinghai Lu wrote:
> real_mode_data aka zero-page could be above 4g.
I think this could be more informative if it said 'struct boot_params'
instead of real_mode_data because real_mode_data is the argument name
passed to the respective function and grepping for struct boot_params
actually gives you the struct definition with the helpful comments and
offsets in arch/x86/include/uapi/asm/bootparam.h.
> We will have #PF handler to set page table for not accessible ram
> early, but could limit it before x86_64_start_reservations to limit
> the change to native path.
>
> Also we will need to ramdisk info in zero-page to access microcode
s/to/the/ ^
the
> blob in ramdisk in x86_64_start_kernel, so copy zero-page early make
makes
> it accessing ramdisk info simple.
>
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
> Cc: Alexander Duyck <alexander.h.duyck@...el.com>
> Cc: Fenghua Yu <fenghua.yu@...el.com>
--
Regards/Gruss,
Boris.
--
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