From: Sohil Mehta <sohil.mehta@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
<linux-kernel@vger.kernel.org>
Cc: Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>, <x86@kernel.org>,
Yeoreum Yun <yeoreum.yun@arm.com>
Subject: Re: [PATCH] x86/mm: Introduce helper for checking direct map 1G page support
Date: Wed, 2 Sep 2026 17:34:33 -0700 [thread overview]
Message-ID: <ff13fe1e-59e3-42f4-a438-bbd3cfbd94c9@intel.com> (raw)
In-Reply-To: <20260902194718.E1FF3041@davehans-spike.ostc.intel.com>
On 9/2/2026 12:47 PM, Dave Hansen wrote:
>
> From: Dave Hansen <dave.hansen@linux.intel.com>
>
> There is an existing variable (direct_gbpages) that says whether the
> kernel can and should use 1G pages in the direct map. It is driven
> by a bunch of other machinery. At least:
>
> 1. Hardware support for 1G pages
> 2. Kconfig support for 1G direct mappings
> 3. Kernel command line overrides
>
> Most code just checks the 'direct_gbpages' variable itself. But there
> are cases where 1G mappings are compile-time disabled (via
> X86_DIRECT_GBPAGES) and 'direct_gbpages' is always 0. Unfortunately,
> that constraint is invisible to the compiler.
>
> This opacity has been historically functionally harmless; it only
> leaves a bit of dead code. But, there are plans to tigthen up the
s/tigthen/tighten
> compile-time checks around folded page table levels. The build will
> break if that dead code appears reachable to the compiler. Making
> the compile-time config visible to the compiler fixes the build.
>
> Add a helper to replace 'direct_gbpages' checks. Check the Kconfig
> option and base CPU support before looking at the variable.
>
It is a bit confusing when this variable is finalized and when the
helper can be called. I was assuming that early __init code modifies the
variable and later code consumes the helper.
That is mostly true except for probe_page_size_mask() which is an __init
consumer as well as a modifier. I don't see any functional issue. But it
may be worthy of a code comment to avoid future issues.
> This lets the compiler optimize things better, especially
> collapse_pud_page() where most of the function can now be optimized
> out when the PUD level is folded.
>
The Link: tag below mentions [1]. Did you mean to reference it here?
> Notes:
>
> Use boot_cpu_has() instead of cpu_feature_enabled(). There's no
> required/disabled features for 1G pages themselves
> (X86_DIRECT_GBPAGES is for kernel mappings only) and the
> static_cpu_has() infrastructure is just gets in the compiler's way.
>
s/is//
> This makes 64-bit build marginally larger (20 bytes in one compile)
> and 32-bit builds less marginally _smaller_ (~700 bytes).
>
> Signed-off-by: Dave Hansen <dave.hansen@linux.intel.com>
> Reviewed-by: Yeoreum Yun <yeoreum.yun@arm.com>
> Tested-by: Yeoreum Yun <yeoreum.yun@arm.com>
> Link: https://lore.kernel.org/all/20260902-dummy_ptxp3-v3-15-5d8f5b17c25c@arm.com/ [1]
> ---
>
> b/arch/x86/include/asm/pgtable.h | 14 ++++++++++++++
> b/arch/x86/kernel/cpu/common.c | 2 +-
> b/arch/x86/kernel/machine_kexec_64.c | 2 +-
> b/arch/x86/mm/init.c | 2 +-
> b/arch/x86/mm/pat/set_memory.c | 4 ++--
> 5 files changed, 19 insertions(+), 5 deletions(-)
>
Overall, the changes look good to me.
Reviewed-by: Sohil Mehta <sohil.mehta@intel.com>
> diff -puN arch/x86/include/asm/pgtable.h~direct_gbpages-compiletime arch/x86/include/asm/pgtable.h
> --- a/arch/x86/include/asm/pgtable.h~direct_gbpages-compiletime 2026-09-02 10:08:59.999169372 -0700
> +++ b/arch/x86/include/asm/pgtable.h 2026-09-02 10:09:00.011170394 -0700
> @@ -1163,6 +1163,20 @@ static inline int pgd_none(pgd_t pgd)
> #ifndef __ASSEMBLER__
>
> extern int direct_gbpages;
> +static inline bool direct_gbpages_enabled(void)
> +{
> + /* Check the direct map config option: */
> + if (!IS_ENABLED(CONFIG_X86_DIRECT_GBPAGES))
> + return false;
> +
> + /* Check the CPU feature: */
> + if (!boot_cpu_has(X86_FEATURE_GBPAGES))
> + return false;
> +
The first two comments don't add much beyond the code. Would it be
useful to say why boot_cpu_has() instead of static_cpu_has() over here
(mainly to avoid accidental cleanup)?
> + /* Check the command-line and early setup variable: */
> + return direct_gbpages;
> +}
> +
> void init_mem_mapping(void);
> void early_alloc_pgt_buf(void);
> void __init poking_init(void);
> diff -puN arch/x86/kernel/machine_kexec_64.c~direct_gbpages-compiletime arch/x86/kernel/machine_kexec_64.c
> --- a/arch/x86/kernel/machine_kexec_64.c~direct_gbpages-compiletime 2026-09-02 10:09:00.004169798 -0700
> +++ b/arch/x86/kernel/machine_kexec_64.c 2026-09-02 10:09:00.012170479 -0700
> @@ -257,7 +257,7 @@ static int init_pgtable(struct kimage *i
> info.kernpg_flag |= _PAGE_ENC;
> }
>
> - if (direct_gbpages)
> + if (direct_gbpages_enabled())
> info.direct_gbpages = true;
>
How about:
info.direct_gbpages = direct_gbpages_enabled()
> for (i = 0; i < nr_pfn_mapped; i++) {
next prev parent reply other threads:[~2026-09-03 0:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 19:47 Dave Hansen
2026-09-03 0:34 ` Sohil Mehta [this message]
2026-09-03 14:05 ` Dave Hansen
2026-09-03 17:52 ` Sohil Mehta
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=ff13fe1e-59e3-42f4-a438-bbd3cfbd94c9@intel.com \
--to=sohil.mehta@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=yeoreum.yun@arm.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
all inboxes | Powered by JetHome®