From: Yves-Alexis Perez <corsac@debian.org>
To: Yang Shi <yang@os.amperecomputing.com>,
willy@infradead.org, jirislaby@kernel.org, surenb@google.com,
riel@surriel.com, cl@linux.com, carnil@debian.org,
ben@decadent.org.uk, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines
Date: Fri, 19 Jul 2024 11:19:24 +0200 [thread overview]
Message-ID: <e4e878901db1336c44ce17939c920119b9912fed.camel@debian.org> (raw)
In-Reply-To: <20240712155855.1130330-1-yang@os.amperecomputing.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On Fri, 2024-07-12 at 08:58 -0700, Yang Shi wrote:
> Yves-Alexis Perez reported commit 4ef9ad19e176 ("mm: huge_memory: don't
> force huge page alignment on 32 bit") didn't work for x86_32 [1]. It is
> because x86_32 uses CONFIG_X86_32 instead of CONFIG_32BIT.
>
> !CONFIG_64BIT should cover all 32 bit machines.
Hi,
I've noticed that the patch was integrated into the -mm tree and next/master.
It's not yet in the first half of the merge window for 6.11 but do you know if
it's scheduled for rc1?
Regards,
- --
Yves-Alexis
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmaaL5wACgkQ3rYcyPpX
RFtzIQf8Dn0wqm4ZDeAvoxX+xPTn5Qhu5T1tDZfnryL584DRroe5PyYr5uI+BL7W
oMfPc+cNYUmGRPc8qmbAhg5K18xlfmPfUDq4idWzLMjpUnmEZflWgrGFvRgJmTo5
Kq2MRxpLi38M9GTeqG3MKtWxouKilch9n1ukmQhV9H0DUtiiS3EhITt9X7PbJ7Zc
yvPtdRcdHXRXSl0x/0hztQy4xuKSJxGQULGoSL0HyS8R9OCj+0hDFgEz98YkSbYW
6pZ8+iZLc+OXEkjKfC3uwI/q0Dw3eZW1zIyPn7ahYteisBr+HfKwoGz7UNzw3aB4
/BB3VA+A7/ikJ9NIwjgSlGTmZso73A==
=1puG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2024-07-19 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 15:58 [PATCH] mm: huge_memory: use !CONFIG_64BIT to relax huge page alignment on 32 bit machines Yang Shi
2024-07-13 1:20 ` David Hildenbrand
2024-07-19 9:19 ` Yves-Alexis Perez [this message]
2024-07-19 20:46 ` Andrew Morton
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=e4e878901db1336c44ce17939c920119b9912fed.camel@debian.org \
--to=corsac@debian.org \
--cc=akpm@linux-foundation.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=cl@linux.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=willy@infradead.org \
--cc=yang@os.amperecomputing.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;
as well as URLs for NNTP newsgroup(s).