From: "David Hildenbrand (Arm)" <david@kernel.org>
To: shao.mingyin@zte.com.cn, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, ziy@nvidia.com, matthew.brost@intel.com,
joshua.hahnjy@gmail.com, byungchul@sk.com, gourry@gourry.net,
ying.huang@linux.alibaba.com, apopple@nvidia.com,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v2] mm/migrate: fix softlockup in do_pages_move() with huge page arrays
Date: Mon, 9 Nov 2026 13:45:32 +0100 [thread overview]
Message-ID: <96984f8b-76be-4a41-9f4a-3e84b29fb1ab@kernel.org> (raw)
In-Reply-To: <20261109203320542JEYrsjSWEO22mMpmG7U_n@zte.com.cn>
On 11/9/26 13:33, shao.mingyin@zte.com.cn wrote:
> Hi David,
>
> fair enough -- and your reading is correct: preempt=none is unselectable
> under PREEMPT_DYNAMIC, and the arches that can still pick PREEMPT_NONE
> have no NUMA, so mainline cannot reach this path.
>
> I was aiming at the 6.6 LTS configs that shipped PREEMPT_NONE + NUMA: two
> lines of cond_resched(), no behaviour change, same as do_pages_stat() got
> in 8e934ab44389. If you and Andrew would rather not carry a stable-only
> fix, just say so and I will withdraw it.
I think this one will be the last ones where we do that and don't really have a
real workload run into it.
It's not a good use of our time and it doesn't make upstream any better :)
--
Cheers,
David
next prev parent reply other threads:[~2026-11-09 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 6:28 [PATCH v2] mm/migrate: fix softlockup in do_pages_move() with huge page arrays shao.mingyin
2026-11-09 12:19 ` David Hildenbrand (Arm)
2026-11-09 12:33 ` shao.mingyin
2026-11-09 12:45 ` David Hildenbrand (Arm) [this message]
2026-11-09 12:56 ` David Hildenbrand
2026-11-10 2:53 ` Zi Yan
2026-11-14 17:51 ` Lorenzo Stoakes (ARM)
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=96984f8b-76be-4a41-9f4a-3e84b29fb1ab@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=byungchul@sk.com \
--cc=gourry@gourry.net \
--cc=joshua.hahnjy@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=shao.mingyin@zte.com.cn \
--cc=stable@vger.kernel.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.