From: Andrew Morton <akpm@linux-foundation.org>
To: Hui Su <sh_def@163.com>,
apopple@nvidia.com, balbirs@nvidia.com, byungchul@sk.com,
david@kernel.org, gourry@gourry.net, joshua.hahnjy@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
matthew.brost@intel.com, rakie.kim@sk.com,
ying.huang@linux.alibaba.com, ziy@nvidia.com
Subject: Re: [PATCH] mm/migrate_device: fix cache flush when replacing huge zero PMD
Date: Mon, 17 Aug 2026 15:12:04 -0700 [thread overview]
Message-ID: <20260817151204.50749d6a3e16e322e6f05d7d@linux-foundation.org> (raw)
In-Reply-To: <20260817143415.60bedb09819d13a2dc0fbe63@linux-foundation.org>
On Mon, 17 Aug 2026 14:34:15 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
> > Hi,
> >
> > I took a closer look at this, there is no userspace-visible effect today.
> >
> > The architectures that currently enable ARCH_ENABLE_THP_MIGRATION use
> > no-op implementations of flush_cache_page()/flush_cache_range().
> > 32-bit ARM has non-trivial implementations, but does not enable
> > ARCH_ENABLE_THP_MIGRATION.
> >
> > So this appears to be a latent API misuse rather than a currently
> > observable bug, and I don't think a stable backport is necessary.
>
> OK, thanks for checking.
>
> > Should I resend a v2 clarifying the userspace-visible effect in the
> > changelog?
>
> Yes please, after 7.3-rc1.
Actually, I updated the changelog and added it to next week's
queue-for-Linus.
next prev parent reply other threads:[~2026-08-17 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 6:08 Hui Su
2026-08-17 7:35 ` Balbir Singh
2026-08-17 16:06 ` Andrew Morton
2026-08-17 16:36 ` Hui Su
2026-08-17 21:34 ` Andrew Morton
2026-08-17 22:06 ` Balbir Singh
2026-08-17 22:12 ` Andrew Morton [this message]
2026-08-17 16:39 ` Zi Yan
2026-08-17 17:47 ` David Hildenbrand (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=20260817151204.50749d6a3e16e322e6f05d7d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=byungchul@sk.com \
--cc=david@kernel.org \
--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=rakie.kim@sk.com \
--cc=sh_def@163.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®