From: Borislav Petkov <bp@alien8.de>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: lkp@intel.com, ardb@kernel.org, brijesh.singh@amd.com,
corbet@lwn.net, dave.hansen@linux.intel.com, hpa@zytor.com,
jan.kiszka@siemens.com, jgross@suse.com, kbingham@kernel.org,
linux-doc@vger.kernel.org, linux-efi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
luto@kernel.org, michael.roth@amd.com, mingo@redhat.com,
oe-kbuild-all@lists.linux.dev, peterz@infradead.org,
rick.p.edgecombe@intel.com, sandipan.das@amd.com,
tglx@linutronix.de, thomas.lendacky@amd.com, x86@kernel.org
Subject: Re: [PATCH] x86/64/mm: Make 5-level paging support unconditional
Date: Wed, 26 Jun 2024 12:46:48 +0200 [thread overview]
Message-ID: <20240626104648.GBZnvxmMXCZbEhoqls@fat_crate.local> (raw)
In-Reply-To: <20240626102624.1059275-1-kirill.shutemov@linux.intel.com>
On Wed, Jun 26, 2024 at 01:26:23PM +0300, Kirill A. Shutemov wrote:
> Both Intel and AMD CPUs support 5-level paging, which is expected to
> become more widely adopted in the future.
>
> Remove CONFIG_X86_5LEVEL and ifdeffery for it to make it more readable.
>
> Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
> Suggested-by: Borislav Petkov <bp@alien8.de>
> ---
>
> v2:
> - Fix 32-bit build by wrapping p4d_set_huge() and p4d_clear_huge() in
> #if CONFIG_PGTABLE_LEVELS > 4
Is the 0day bot smart enough to detect separate v2 fixups like that and
re-test using them?
If not, you can push your tree to your repo so that it can chew on it again
and report any other potential breakages...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2024-06-26 10:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240621164406.256314-4-kirill.shutemov@linux.intel.com>
2024-06-25 23:21 ` [PATCH 3/3] " kernel test robot
[not found] ` <20240626102624.1059275-1-kirill.shutemov@linux.intel.com>
2024-06-26 10:46 ` Borislav Petkov [this message]
2024-06-26 12:00 ` [PATCH] " 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=20240626104648.GBZnvxmMXCZbEhoqls@fat_crate.local \
--to=bp@alien8.de \
--cc=ardb@kernel.org \
--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=lkp@intel.com \
--cc=luto@kernel.org \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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