From: Dave Hansen <dave.hansen@intel.com>
To: "Oscar Salvador (SUSE)" <osalvador@kernel.org>,
Karsten Desler <kdesler@soohrt.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [REGRESSION] x86/hugetlb: AMD F15h VA alignment offset breaks MAP_HUGETLB alignment
Date: Wed, 27 May 2026 14:04:10 -0700 [thread overview]
Message-ID: <5f70e840-9d0e-4cef-8574-b355cf26e0c4@intel.com> (raw)
In-Reply-To: <ahc31AChKqnfItHW@localhost.localdomain>
On 5/27/26 11:28, Oscar Salvador (SUSE) wrote:
> if (filp) {
> info.align_mask = get_align_mask(filp);
> - info.align_offset += get_align_bits();
> + /*
> + * Hugepages must remain hugepage-aligned, so skip adding an offset
> + * in case we enabled 'align_va_addr'.
> + */
> + if (!is_file_hugepages(filp))
> + info.align_offset += get_align_bits();
> }
That's a good hack to show the scope of the problem.
But I'd really rather this be dealt with in the arch-independent code,
not by adding hugetlb hacks to arch code. It isn't even clear to me what
exactly goes wrong when you set a tiny ->align_offset and have a larger
->align_mask. Shouldn't the tiny offset just get masked off?
gap += (info->align_offset - gap) & info->align_mask;
I spent a whole five seconds looking at it, but something seems to be
missing from the problem description.
next prev parent reply other threads:[~2026-05-27 21:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 14:36 Karsten Desler
2026-05-27 15:53 ` Oscar Salvador (SUSE)
2026-05-27 18:28 ` Oscar Salvador (SUSE)
2026-05-27 20:39 ` Karsten Desler
2026-05-27 21:04 ` Dave Hansen [this message]
2026-05-28 5:45 ` Oscar Salvador (SUSE)
2026-05-28 12:45 ` Oscar Salvador (SUSE)
2026-05-28 14:03 ` Oscar Salvador (SUSE)
2026-05-28 15:31 ` Borislav Petkov
2026-05-28 18:29 ` Oscar Salvador (SUSE)
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=5f70e840-9d0e-4cef-8574-b355cf26e0c4@intel.com \
--to=dave.hansen@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kdesler@soohrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=osalvador@kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome