On Tue, Jul 7, 2015 at 1:20 PM, Yinghai Lu <[email protected]> wrote: > remove not needed clear_page for init_level4_page in x86_64_start_kernel(), > as it is with fill 512,8,0 already in head_64.S
Will all possible entry points have come through head_64.S? -Kees > > Signed-off-by: Yinghai Lu <[email protected]> > --- > arch/x86/kernel/head64.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c > index 44dc63b..a9f0299 100644 > --- a/arch/x86/kernel/head64.c > +++ b/arch/x86/kernel/head64.c > @@ -178,7 +178,6 @@ asmlinkage __visible void __init x86_64_start_kernel(char > * real_mode_data) > */ > load_ucode_bsp(); > > - clear_page(init_level4_pgt); > /* set init_level4_pgt kernel high mapping*/ > init_level4_pgt[511] = early_level4_pgt[511]; > > -- > 1.8.4.5 > > -- > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [email protected] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
