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 <ying...@kernel.org>
> Cc: Alexander Duyck <alexander.h.du...@intel.com>
> Cc: Fenghua Yu <fenghua...@intel.com>
--
Regards/Gruss,
Boris.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
