From: SJ Park <sj@kernel.org>
To: SJ Park <sj@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org,
Baolin Wang <baolin.wang@linux.alibaba.com>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH] mm/damon/vaddr: avoid hw-driven pte updates during damon_hugetlb_mkold()
Date: Mon, 7 Sep 2026 11:08:20 -0700 [thread overview]
Message-ID: <20260907180821.102875-1-sj@kernel.org> (raw)
In-Reply-To: <20260907170358.100168-1-sj@kernel.org>
On Mon, 7 Sep 2026 10:03:56 -0700 SJ Park <sj@kernel.org> wrote:
[...]
> +static bool damon_hugetlb_ptep_mkold(pte_t *pte, struct mm_struct *mm,
> + struct vm_area_struct *vma, unsigned long addr, pte_t *entry)
> +{
> + unsigned long psize = huge_page_size(hstate_vma(vma));
> +
> + if (!pte_young(*entry))
> + return false;
> + *entry = huge_ptep_get_and_clear(mm, addr, pte, psize);
> + *entry = pte_mkold(*entry);
> + set_huge_pte_at(mm, addr, pte, *entry, psize);
> + return true;
Sashiko says [1] this might violate BBM. But this is only for accessed bit
change. So I don't think BBM is required here. Also, we intentionally do not
flush TLB because this is just a best-effort monitoring. Please correct me if
I'm wrong.
[1] https://lore.kernel.org/20260907171613.A09B11F00A3A@smtp.kernel.org
Thanks,
SJ
[...]
prev parent reply other threads:[~2026-09-07 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 17:03 [PATCH] mm/damon/vaddr: avoid hw-driven pte updates during damon_hugetlb_mkold() SJ Park
2026-09-07 17:16 ` sashiko-bot
2026-09-07 18:04 ` SJ Park
2026-09-07 18:08 ` SJ Park [this message]
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=20260907180821.102875-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
/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.