From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Khalid Ali <khaliidcaliy@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
dave.hansen@linux.intel.com, hpa@zytor.com, corbet@lwn.net,
luto@kernel.org, peterz@infradead.org, ardb@kernel.org,
jan.kiszka@siemens.com, kbingham@kernel.org,
michael.roth@amd.com, rick.p.edgecombe@intel.com,
brijesh.singh@amd.com, sandipan.das@amd.com, jgross@suse.com,
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 0/3] x86: Make 5-level paging support unconditional for x86-64
Date: Tue, 24 Jun 2025 11:49:45 +0300 [thread overview]
Message-ID: <m3i4z5ell2lhtpverw5slnxidd32lmtqcdpwcljtr5betki6s5@kiq2bibj5lt2> (raw)
In-Reply-To: <20250624081400.2284-1-khaliidcaliy@gmail.com>
On Tue, Jun 24, 2025 at 08:11:15AM +0000, Khalid Ali wrote:
> This will break x86_64 cpus that doesn't support 5-level paging.
No, it won't.
The patchset removes compile-time config option to disable 5-level paging.
After tha patchset all kernels will be built with 5-level paging *support*.
The actual paging mode is chosen at boot time based on machine
capabilities and kernel command line. Older HW will boot in 4-level paging
mode just fine.
--
Kiryl Shutsemau / Kirill A. Shutemov
next prev parent reply other threads:[~2025-06-24 8:49 UTC|newest]
Thread overview: 17+ 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 ` [PATCHv2 2/3] x86/64/mm: Make SPARSEMEM_VMEMMAP the only memory model Ard Biesheuvel
[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 [this message]
[not found] <20250516123306.3812286-1-kirill.shutemov@linux.intel.com>
2025-06-24 8:23 ` Khalid Ali
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=m3i4z5ell2lhtpverw5slnxidd32lmtqcdpwcljtr5betki6s5@kiq2bibj5lt2 \
--to=kirill.shutemov@linux.intel.com \
--cc=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=khaliidcaliy@gmail.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 \
/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