public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.ibm.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: x86@kernel.org, hpa@zytor.com,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Joerg Roedel <jroedel@suse.de>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/3] x86/mm: Pre-allocate p4d/pud pages for vmalloc area
Date: Tue, 21 Jul 2020 13:44:54 +0300	[thread overview]
Message-ID: <20200721104454.GF802087@linux.ibm.com> (raw)
In-Reply-To: <20200721095953.6218-2-joro@8bytes.org>

On Tue, Jul 21, 2020 at 11:59:51AM +0200, Joerg Roedel wrote:
> From: Joerg Roedel <jroedel@suse.de>
> 
> Pre-allocate the page-table pages for the vmalloc area at the level
> which needs synchronization on x86-64, which is P4D for 5-level and
> PUD for 4-level paging.
> 
> Doing this at boot makes sure all no synchronization of that area is

Nit:                           ^all can be dropped
 
> necessary at runtime. The synchronization takes the pgd_lock and
> iterates over all page-tables in the system, so it can take quite long
> and is better avoided.
> 
> Signed-off-by: Joerg Roedel <jroedel@suse.de>
> ---
>  arch/x86/mm/init_64.c | 52 +++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 52 insertions(+)
> 
> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> index dbae185511cd..e76bdb001460 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -1238,6 +1238,56 @@ static void __init register_page_bootmem_info(void)
>  #endif
>  }
>  
> +/*
> + * Pre-allocates page-table pages for the vmalloc area in the kernel page-table.
> + * Only the level which needs to be synchronized between all page-tables is
> + * allocated because the synchronization can be expensive.
> + */
> +static void __init preallocate_vmalloc_pages(void)
> +{
> +	unsigned long addr;
> +	const char *lvl;
> +
> +	for (addr = VMALLOC_START; addr <= VMALLOC_END; addr = ALIGN(addr + 1, PGDIR_SIZE)) {
> +		pgd_t *pgd = pgd_offset_k(addr);
> +		p4d_t *p4d;
> +		pud_t *pud;
> +
> +		p4d = p4d_offset(pgd, addr);
> +		if (p4d_none(*p4d)) {
> +			/* Can only happen with 5-level paging */
> +			p4d = p4d_alloc(&init_mm, pgd, addr);
> +			if (!p4d) {
> +				lvl = "p4d";
> +				goto failed;
> +			}
> +		}
> +
> +		if (pgtable_l5_enabled())
> +			continue;
> +
> +		pud = pud_offset(p4d, addr);
> +		if (pud_none(*pud)) {
> +			/* Ends up here only with 4-level paging */
> +			pud = pud_alloc(&init_mm, p4d, addr);
> +			if (!pud) {
> +				lvl = "pud";
> +				goto failed;
> +			}
> +		}
> +	}
> +
> +	return;
> +
> +failed:
> +
> +	/*
> +	 * The pages have to be there now or they will be missing in
> +	 * process page-tables later.
> +	 */
> +	panic("Failed to pre-allocate %s pages for vmalloc area\n", lvl);
> +}
> +
>  void __init mem_init(void)
>  {
>  	pci_iommu_alloc();
> @@ -1261,6 +1311,8 @@ void __init mem_init(void)
>  	if (get_gate_vma(&init_mm))
>  		kclist_add(&kcore_vsyscall, (void *)VSYSCALL_ADDR, PAGE_SIZE, KCORE_USER);
>  
> +	preallocate_vmalloc_pages();
> +
>  	mem_init_print_info(NULL);
>  }
>  
> -- 
> 2.27.0
> 

-- 
Sincerely yours,
Mike.

  reply	other threads:[~2020-07-21 10:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  9:59 [PATCH v3 0/3] x86/mm/64: Remove vmalloc/ioremap pgtable synchronization Joerg Roedel
2020-07-21  9:59 ` [PATCH v3 1/3] x86/mm: Pre-allocate p4d/pud pages for vmalloc area Joerg Roedel
2020-07-21 10:44   ` Mike Rapoport [this message]
2020-07-27 12:46   ` [tip: x86/mm] x86/mm: Pre-allocate P4D/PUD " tip-bot2 for Joerg Roedel
2020-07-21  9:59 ` [PATCH v3 2/3] x86/mm/64: Do not sync vmalloc/ioremap mappings Joerg Roedel
2020-07-27 12:46   ` [tip: x86/mm] " tip-bot2 for Joerg Roedel
2020-07-21  9:59 ` [PATCH v3 3/3] x86/mm/64: Make sync_global_pgds() static Joerg Roedel
2020-07-27 12:46   ` [tip: x86/mm] " tip-bot2 for Joerg Roedel
2020-07-21 10:44 ` [PATCH v3 0/3] x86/mm/64: Remove vmalloc/ioremap pgtable synchronization Mike Rapoport
2020-07-27 11:08 ` Ingo Molnar

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=20200721104454.GF802087@linux.ibm.com \
    --to=rppt@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=joro@8bytes.org \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@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