From: Kyle Meyer <kyle.meyer@hpe.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>
Cc: Liam.Howlett@oracle.com, akpm@linux-foundation.org, bp@alien8.de,
corbet@lwn.net, david@redhat.com, hannes@cmpxchg.org,
jack@suse.cz, jane.chu@oracle.com, jiaqiyan@google.com,
joel.granados@kernel.org, laoar.shao@gmail.com,
linmiaohe@huawei.com, linux-acpi@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
lorenzo.stoakes@oracle.com, mclapinski@google.com,
mhocko@suse.com, nao.horiguchi@gmail.com, osalvador@suse.de,
rafael.j.wysocki@intel.com, rppt@kernel.org,
russ.anderson@hpe.com, shawn.fan@intel.com, shuah@kernel.org,
surenb@google.com, tony.luck@intel.com, vbabka@suse.cz
Subject: Re: [PATCH v2] mm/memory-failure: Support disabling soft offline for HugeTLB pages
Date: Mon, 24 Aug 2026 12:53:47 -0500 [thread overview]
Message-ID: <aoyFK92azAlDAPuF@hpe.com> (raw)
In-Reply-To: <0d2fc2ab-333e-42a1-88a1-6bb85538cbb0@linux.alibaba.com>
On Thu, Aug 20, 2026 at 11:47:11AM +0800, Shuai Xue wrote:
> Hi Kyle,
Hi.
> Following up on this thread. The v2 patch once landed in akpm's mm
> tree (9ae6eefa4b6b "mm/memory-failure: support disabling soft
> offline for HugeTLB pages"), but that commit is now not reachable
> from any branch, and mainline as of v7.3-rc1 still only has the 0/1
> switch in /proc/sys/vm/enable_soft_offline.
Thanks for pointing this out.
Looks like this patch was added on 2025-09-16 [1] and dropped on 2025-11-11 [2].
[1] https://lore.kernel.org/all/20250916032512.AE588C4CEEB@smtp.kernel.org
[2] https://lore.kernel.org/all/20251111231818.52A60C16AAE@smtp.kernel.org
I must have missed the second email.
I don't remember discussing a v3. Can someone please remind me what we planned
to change or whether there was another reason it was dropped?
> The underlying issue discussed here is still unresolved for us:
> firmware reporting per-rank corrected error thresholds via GHES
> triggers soft offline of huge pages, which neither addresses the
> failing rank nor is acceptable for workloads that rely on stable
> hugetlb physical layouts.
>
> Do you still plan to send a v3, e.g. with the disable-bitmask
> layout Anshuman suggested upthread?
I wasn't planning on sending a v3 but I'm happy to revisit if needed.
Thanks,
Kyle Meyer
next prev parent reply other threads:[~2026-08-24 18:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 0:27 [PATCH v2] mm/memory-failure: Support disabling soft offline for HugeTLB pages Kyle Meyer
2025-09-16 3:16 ` Andrew Morton
2025-09-16 7:14 ` Kyle Meyer
2025-09-16 15:20 ` Luck, Tony
2025-09-16 17:59 ` Kyle Meyer
2025-09-16 18:08 ` Luck, Tony
2025-09-17 6:35 ` Fan, Shawn
2025-09-17 18:59 ` Kyle Meyer
2025-09-18 8:34 ` Shuai Xue
2025-09-18 15:48 ` Jiaqi Yan
2025-09-16 10:12 ` Anshuman Khandual
2025-09-17 7:02 ` David Hildenbrand
2025-09-17 18:51 ` Kyle Meyer
2025-09-17 19:05 ` David Hildenbrand
2025-09-17 19:32 ` Jiaqi Yan
2025-09-17 19:54 ` Luck, Tony
2025-09-17 21:39 ` Kyle Meyer
2025-09-17 22:15 ` Jiaqi Yan
2025-09-21 11:36 ` Anshuman Khandual
2025-09-23 6:03 ` Kyle Meyer
2025-09-21 11:25 ` Anshuman Khandual
2026-08-20 3:47 ` Shuai Xue
2026-08-24 17:53 ` Kyle Meyer [this message]
2026-08-24 18:20 ` Andrew Morton
2026-08-24 18:31 ` Kyle Meyer
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=aoyFK92azAlDAPuF@hpe.com \
--to=kyle.meyer@hpe.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jane.chu@oracle.com \
--cc=jiaqiyan@google.com \
--cc=joel.granados@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=linmiaohe@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mclapinski@google.com \
--cc=mhocko@suse.com \
--cc=nao.horiguchi@gmail.com \
--cc=osalvador@suse.de \
--cc=rafael.j.wysocki@intel.com \
--cc=rppt@kernel.org \
--cc=russ.anderson@hpe.com \
--cc=shawn.fan@intel.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=tony.luck@intel.com \
--cc=vbabka@suse.cz \
--cc=xueshuai@linux.alibaba.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