Re: [PATCH v3 1/3] x86/64: Make kernel text mapping always take one whole page table in early boot code

From: Boris Petkov
Date: Wed Jan 04 2017 - 10:43:04 EST


On January 4, 2017 10:37:31 AM GMT+02:00, Baoquan He <bhe@xxxxxxxxxx> wrote:
>In early boot code level2_kernel_pgt is used to map kernel text. And
>its
>size varies with KERNEL_IMAGE_SIZE and fixed at compiling time. In fact
>we can make it always take 512 entries of one whole page table, because
>later function cleanup_highmap will clean up the unused entries. With
>the
>help of this change kernel text mapping size can be decided at runtime
>later, 512M if kaslr is disabled, 1G if kaslr is enabled.
Question: so why are we even having that distinction? Why aren't we making text mapping size 1G by default and be done with it?
--
Sent from a small device: formatting sux and brevity is inevitable.