From: Dave Hansen <dave.hansen@intel.com>
To: Laurent Wandrebeck <l.wandrebeck@quelquesmots.fr>,
Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] x86/mm: don't apply va_align to hugetlb mappings on AMD F15h
Date: Mon, 21 Sep 2026 09:19:29 -0700 [thread overview]
Message-ID: <f2e54889-ff66-469c-8144-8a7da2291055@intel.com> (raw)
In-Reply-To: <45dc4a4f62e49107de788b4be9a4039e0d772fa1.camel@quelquesmots.fr>
On 9/19/26 01:47, Laurent Wandrebeck wrote:
> static unsigned long get_align_mask(struct file *filp)
> {
> - if (filp && is_file_hugepages(filp))
> + if (is_file_hugepages(filp))
> return huge_page_mask_align(filp);
> /* handle 32- and 64-bit case with a single conditional */
> if (va_align.flags < 0 || !(va_align.flags & (2 - mmap_is_ia32())))
I'd just leave that hunk out for now. It's harmless to leave.
> @@ -50,9 +50,13 @@ static unsigned long get_align_mask(struct file *filp)
> * value before calling vm_unmapped_area() or ORed directly to the
> * address.
> */
> -static unsigned long get_align_bits(void)
> +static unsigned long get_align_bits(struct file *filp)
> {
> - return va_align.bits & get_align_mask(NULL);
> + /* hugetlb mappings must stay on the huge page boundary. */
> + if (is_file_hugepages(filp))
> + return 0;
I don't find that comment helpful. The function is kinda misnamed a bit
too. Maybe a comment like this?
/*
* va_align.bits is smaller than the huge page size and will
* lead to misaligned huge pages. Ignore it for huge mappings.
*/
> + return va_align.bits & get_align_mask(filp);
> }
>
> static int __init control_va_addr_alignment(char *str)
> @@ -157,7 +161,7 @@ arch_get_unmapped_area(struct file *filp, unsigned long addr, unsigned long len,
> }
> if (filp) {
> info.align_mask = get_align_mask(filp);
> - info.align_offset += get_align_bits();
> + info.align_offset += get_align_bits(filp);
> }
>
> return vm_unmapped_area(&info);
> @@ -222,7 +226,7 @@ arch_get_unmapped_area_topdown(struct file *filp, unsigned long addr0,
>
> if (filp) {
> info.align_mask = get_align_mask(filp);
> - info.align_offset += get_align_bits();
> + info.align_offset += get_align_bits(filp);
> }
That looks fine too. I would rather this whole mechanism die,
personally. But this is a fine, backportable fix.
next prev parent reply other threads:[~2026-09-22 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 13:57 [PATCH] x86/mm: don't apply va_align to hugetlb mappings on AMD F15h Laurent Wandrebeck
2026-08-28 17:07 ` Dave Hansen
2026-08-29 17:47 ` Borislav Petkov
2026-08-29 18:15 ` Laurent Wandrebeck
2026-08-29 18:51 ` Borislav Petkov
2026-09-01 8:12 ` Laurent Wandrebeck
2026-09-16 20:02 ` Borislav Petkov
2026-09-19 8:47 ` Laurent Wandrebeck
2026-09-19 17:53 ` Borislav Petkov
2026-09-21 16:19 ` Dave Hansen [this message]
2026-09-22 8:50 ` [PATCH v2] " Laurent Wandrebeck
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=f2e54889-ff66-469c-8144-8a7da2291055@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=l.wandrebeck@quelquesmots.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=osalvador@suse.de \
--cc=stable@vger.kernel.org \
--cc=tglx@kernel.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