linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ardb@kernel.org>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	 Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org,  "H. Peter Anvin" <hpa@zytor.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Andy Lutomirski <luto@kernel.org>,
	 Peter Zijlstra <peterz@infradead.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	 Kieran Bingham <kbingham@kernel.org>,
	Michael Roth <michael.roth@amd.com>,
	 Rick Edgecombe <rick.p.edgecombe@intel.com>,
	Brijesh Singh <brijesh.singh@amd.com>,
	 Sandipan Das <sandipan.das@amd.com>,
	Juergen Gross <jgross@suse.com>,
	 Tom Lendacky <thomas.lendacky@amd.com>,
	linux-kernel@vger.kernel.org,  linux-doc@vger.kernel.org,
	linux-efi@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCHv2 2/3] x86/64/mm: Make SPARSEMEM_VMEMMAP the only memory model
Date: Fri, 16 May 2025 10:51:55 +0100	[thread overview]
Message-ID: <CAMj1kXGe6jx=dZ3Xe8Cz-xD0pHUaDCyKB4Shb4B=U5vAWXcdRw@mail.gmail.com> (raw)
In-Reply-To: <20250516091534.3414310-3-kirill.shutemov@linux.intel.com>

On Fri, 16 May 2025 at 10:15, Kirill A. Shutemov
<kirill.shutemov@linux.intel.com> wrote:
>
> 5-level paging only supports SPARSEMEM_VMEMMAP. CONFIG_X86_5LEVEL is
> being phased out, making 5-level paging support mandatory.
>
> Make CONFIG_SPARSEMEM_VMEMMAP mandatory for x86-64 and eliminate
> any associated conditional statements.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>

Reviewed-by: Ard Biesheuvel <ardb@kernel.org>

> ---
>  arch/x86/Kconfig      | 2 +-
>  arch/x86/mm/init_64.c | 9 +--------
>  2 files changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index d3c2da3b2f0b..45b36a019b5e 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -1467,7 +1467,6 @@ config X86_PAE
>  config X86_5LEVEL
>         bool "Enable 5-level page tables support"
>         default y
> -       select SPARSEMEM_VMEMMAP
>         depends on X86_64
>         help
>           5-level paging enables access to larger address space:
> @@ -1579,6 +1578,7 @@ config ARCH_SPARSEMEM_ENABLE
>         def_bool y
>         select SPARSEMEM_STATIC if X86_32
>         select SPARSEMEM_VMEMMAP_ENABLE if X86_64
> +       select SPARSEMEM_VMEMMAP if X86_64
>
>  config ARCH_SPARSEMEM_DEFAULT
>         def_bool X86_64 || (NUMA && X86_32)
> diff --git a/arch/x86/mm/init_64.c b/arch/x86/mm/init_64.c
> index bf45c7aed336..66330fe4e18c 100644
> --- a/arch/x86/mm/init_64.c
> +++ b/arch/x86/mm/init_64.c
> @@ -833,7 +833,6 @@ void __init paging_init(void)
>         zone_sizes_init();
>  }
>
> -#ifdef CONFIG_SPARSEMEM_VMEMMAP
>  #define PAGE_UNUSED 0xFD
>
>  /*
> @@ -932,7 +931,6 @@ static void __meminit vmemmap_use_new_sub_pmd(unsigned long start, unsigned long
>         if (!IS_ALIGNED(end, PMD_SIZE))
>                 unused_pmd_start = end;
>  }
> -#endif
>
>  /*
>   * Memory hotplug specific functions
> @@ -1152,16 +1150,13 @@ remove_pmd_table(pmd_t *pmd_start, unsigned long addr, unsigned long end,
>                                 pmd_clear(pmd);
>                                 spin_unlock(&init_mm.page_table_lock);
>                                 pages++;
> -                       }
> -#ifdef CONFIG_SPARSEMEM_VMEMMAP
> -                       else if (vmemmap_pmd_is_unused(addr, next)) {
> +                       } else if (vmemmap_pmd_is_unused(addr, next)) {
>                                         free_hugepage_table(pmd_page(*pmd),
>                                                             altmap);
>                                         spin_lock(&init_mm.page_table_lock);
>                                         pmd_clear(pmd);
>                                         spin_unlock(&init_mm.page_table_lock);
>                         }
> -#endif
>                         continue;
>                 }
>
> @@ -1500,7 +1495,6 @@ unsigned long memory_block_size_bytes(void)
>         return memory_block_size_probed;
>  }
>
> -#ifdef CONFIG_SPARSEMEM_VMEMMAP
>  /*
>   * Initialise the sparsemem vmemmap using huge-pages at the PMD level.
>   */
> @@ -1647,4 +1641,3 @@ void __meminit vmemmap_populate_print_last(void)
>                 node_start = 0;
>         }
>  }
> -#endif
> --
> 2.47.2
>


  parent reply	other threads:[~2025-05-16  9:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250516091534.3414310-1-kirill.shutemov@linux.intel.com>
     [not found] ` <20250516091534.3414310-2-kirill.shutemov@linux.intel.com>
2025-05-16  9:50   ` [PATCHv2 1/3] x86/64/mm: Always use dynamic memory layout Ard Biesheuvel
     [not found] ` <20250516091534.3414310-3-kirill.shutemov@linux.intel.com>
2025-05-16  9:51   ` Ard Biesheuvel [this message]
     [not found] ` <20250516091534.3414310-4-kirill.shutemov@linux.intel.com>
2025-05-16  9:54   ` [PATCHv2 3/3] x86/64/mm: Make 5-level paging support unconditional Ard Biesheuvel
2025-05-16 10:42   ` Jürgen Groß
2025-05-16 11:09     ` Kirill A. Shutemov
2025-05-16 11:29       ` Jürgen Groß
2025-05-16 11:47         ` Kirill A. Shutemov
2025-05-16 11:51           ` Juergen Gross
2025-05-16 11:51           ` Kirill A. Shutemov
2025-05-16 15:30   ` Borislav Petkov
2025-05-16 15:46     ` Ingo Molnar
2025-05-16 15:56       ` Borislav Petkov
2025-05-17  8:44         ` Ingo Molnar
2025-06-24  8:11 ` [PATCHv2 0/3] x86: Make 5-level paging support unconditional for x86-64 Khalid Ali
2025-06-24  8:22   ` H. Peter Anvin
2025-06-24  8:49   ` Kirill A. Shutemov

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='CAMj1kXGe6jx=dZ3Xe8Cz-xD0pHUaDCyKB4Shb4B=U5vAWXcdRw@mail.gmail.com' \
    --to=ardb@kernel.org \
    --cc=bp@alien8.de \
    --cc=brijesh.singh@amd.com \
    --cc=corbet@lwn.net \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jgross@suse.com \
    --cc=kbingham@kernel.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=michael.roth@amd.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sandipan.das@amd.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --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