public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Alexnader Kuleshov <kuleshovmail@gmail.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, hpa@zytor.com,
	mingo@redhat.com, x86@kernel.org, keescook@chromium.org,
	yinghai@kernel.org, bp@suse.de, thgarnie@google.com,
	luto@kernel.org, anderson@redhat.com, dyoung@redhat.com,
	xlpang@redhat.com
Subject: Re: [PATCH 1/2] x86/64: Make kernel text mapping always take one whole page table in early boot code
Date: Thu, 8 Dec 2016 16:40:00 +0800	[thread overview]
Message-ID: <20161208084000.GB3328@x1> (raw)
In-Reply-To: <20161208082432.GB3998@localhost.localdomain>

On 12/08/16 at 02:24pm, Alexnader Kuleshov wrote:
> On 12-08-16, Baoquan He wrote:
> > In early boot code level2_kernel_pgt is used to map kernel text. And its
> > size varies according to KERNEL_IMAGE_SIZE and fixed at compiling time.
> > In fact we can make it always takes 512 entries of one whople 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.
> 
> s/whople/whole

Will change. Thanks!

> 
> > Signed-off-by: Baoquan He <bhe@redhat.com>
> > ---
> >  arch/x86/include/asm/page_64_types.h |  3 ++-
> >  arch/x86/kernel/head_64.S            | 15 ++++++++-------
> >  arch/x86/mm/init_64.c                |  2 +-
> >  3 files changed, 11 insertions(+), 9 deletions(-)
> > 
> > diff --git a/arch/x86/include/asm/page_64_types.h b/arch/x86/include/asm/page_64_types.h
> > index 9215e05..62a20ea 100644
> > --- a/arch/x86/include/asm/page_64_types.h
> > +++ b/arch/x86/include/asm/page_64_types.h
> > @@ -56,8 +56,9 @@
> >   * are fully set up. If kernel ASLR is configured, it can extend the
> >   * kernel page table mapping, reducing the size of the modules area.
> >   */
> > +#define KERNEL_MAPPING_SIZE_EXT	(1024 * 1024 * 1024)
> >  #if defined(CONFIG_RANDOMIZE_BASE)
> > -#define KERNEL_IMAGE_SIZE	(1024 * 1024 * 1024)
> > +#define KERNEL_IMAGE_SIZE	KERNEL_MAPPING_SIZE_EXT
> >  #else
> >  #define KERNEL_IMAGE_SIZE	(512 * 1024 * 1024)
> >  #endif
> > diff --git a/arch/x86/kernel/head_64.S b/arch/x86/kernel/head_64.S
> > index b4421cc..c4b40e7c9 100644
> > --- a/arch/x86/kernel/head_64.S
> > +++ b/arch/x86/kernel/head_64.S
> > @@ -453,17 +453,18 @@ NEXT_PAGE(level3_kernel_pgt)
> >  
> >  NEXT_PAGE(level2_kernel_pgt)
> >  	/*
> > -	 * 512 MB kernel mapping. We spend a full page on this pagetable
> > -	 * anyway.
> > +	 * Kernel image size is limited to 512 MB. The kernel code+data+bss
> > +	 * must not be bigger than that.
> >  	 *
> > -	 * The kernel code+data+bss must not be bigger than that.
> > +	 * We spend a full page on this pagetable anyway, so take the whole
> > +	 * page here so that the kernel mapping size can be decided at runtime,
> > +	 * 512M if no kaslr, 1G if kaslr enabled. Later cleanup_highmap will
> > +	 * clean up those unused entries.
> >  	 *
> > -	 * (NOTE: at +512MB starts the module area, see MODULES_VADDR.
> > -	 *  If you want to increase this then increase MODULES_VADDR
> > -	 *  too.)
> > +	 * The module area starts after kernel mapping area.
> >  	 */
> >  	PMDS(0, __PAGE_KERNEL_LARGE_EXEC,
> > -		KERNEL_IMAGE_SIZE/PMD_SIZE)
> > +		PTRS_PER_PMD)
> >  
> >  NEXT_PAGE(level2_fixmap_pgt)
> >  	.fill	506,8,0
> > diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> > index 14b9dd7..e95b977 100644
> > --- a/arch/x86/mm/init_64.c
> > +++ b/arch/x86/mm/init_64.c
> > @@ -307,7 +307,7 @@ void __init init_extra_mapping_uc(unsigned long phys, unsigned long size)
> >  void __init cleanup_highmap(void)
> >  {
> >  	unsigned long vaddr = __START_KERNEL_map;
> > -	unsigned long vaddr_end = __START_KERNEL_map + KERNEL_IMAGE_SIZE;
> > +	unsigned long vaddr_end = __START_KERNEL_map + KERNEL_MAPPING_SIZE_EXT;
> >  	unsigned long end = roundup((unsigned long)_brk_end, PMD_SIZE) - 1;
> >  	pmd_t *pmd = level2_kernel_pgt;
> >  
> > -- 
> > 2.5.5
> > 

  reply	other threads:[~2016-12-08  8:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08  7:56 [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64 Baoquan He
2016-12-08  7:56 ` [PATCH 1/2] x86/64: Make kernel text mapping always take one whole page table in early boot code Baoquan He
2016-12-08  8:24   ` Alexnader Kuleshov
2016-12-08  8:40     ` Baoquan He [this message]
2016-12-08  7:56 ` [PATCH 2/2] x86/KASLR/64: Determine kernel text mapping size at runtime Baoquan He
2016-12-08  8:17   ` Alexnader Kuleshov
2016-12-08  8:25     ` Baoquan He
2016-12-08  9:41   ` kbuild test robot
2016-12-08 13:41     ` Baoquan He
2016-12-08  9:41   ` kbuild test robot
2016-12-08 18:31 ` [PATCH 0/2] Determine kernel text mapping size at runtime for x86_64 Kees Cook
2016-12-08 19:00   ` Dave Anderson
2016-12-10  1:32     ` Baoquan He

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161208084000.GB3328@x1 \
    --to=bhe@redhat.com \
    --cc=anderson@redhat.com \
    --cc=bp@suse.de \
    --cc=dyoung@redhat.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=kuleshovmail@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=thgarnie@google.com \
    --cc=x86@kernel.org \
    --cc=xlpang@redhat.com \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox