From: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
To: Zi Yan <ziy@nvidia.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
akpm@linux-foundation.org, liam@infradead.org,
vbabka@kernel.org, jannh@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Pedro Falcato <pfalcato@suse.de>
Subject: Re: [PATCH] mm/madvise: keep the hardware dirty bit in MADV_COLD's THP path
Date: Mon, 12 Oct 2026 16:26:31 +0100 [thread overview]
Message-ID: <asz7YUXhdmlenXvh@gremlin> (raw)
In-Reply-To: <D964ECBC-59B6-4A4B-83D5-935EA2D06D30@nvidia.com>
+cc Pedro
On Mon, Oct 12, 2026 at 11:17:57AM -0400, Zi Yan wrote:
> On 12 Oct 2026, at 6:38, Lorenzo Stoakes (ARM) wrote:
> > [0]: https://lore.kernel.org/linux-mm/20261009-lazyfree-stable-fix-v1-1-70997958ef8d@nvidia.com
>
> No. Without lazyfree PMD level THP discard, the affect PMD will be split
> into PTEs without dirty bit and the dirty folio is still discarded.
OK thanks for clarifying!
>
> We will need Samarth’s fix for backport, then we can think carefully
> about David’s per-arch solution for mainline.
It's AI slop, and we don't accept that in mm (also -cc slopper).
Somebody from the core team will take of this fix separately.
Pedro - you mentioned you were interested in this, will you send a patch?
--
Cheers, Lorenzo
next prev parent reply other threads:[~2026-10-12 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-11 13:22 [PATCH] mm/madvise: keep the hardware dirty bit in MADV_COLD's THP path samarth.colleges
2026-10-12 10:00 ` Lorenzo Stoakes (ARM)
2026-10-12 10:09 ` David Hildenbrand (Arm)
2026-10-12 10:33 ` Lorenzo Stoakes (ARM)
2026-10-12 10:38 ` Lorenzo Stoakes (ARM)
2026-10-12 15:17 ` Zi Yan
2026-10-12 15:26 ` Lorenzo Stoakes (ARM) [this message]
2026-10-12 19:02 ` Pedro Falcato
2026-10-12 18:25 ` Samarth Narang
2026-10-12 20:00 ` 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=asz7YUXhdmlenXvh@gremlin \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--cc=stable@vger.kernel.org \
--cc=vbabka@kernel.org \
--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.