mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Aveline Noir <jm5905938@gmail.com>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Shubhang Kaushik <sh@gentwo.org>,
	damon@lists.linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, Fernand Sieber <sieberf@amazon.com>,
	Leonard Foerster <foersleo@amazon.de>,
	SeongJae Park <sjpark@amazon.de>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	Shubhang Kaushik <shubhang@os.amperecomputing.com>,
	Christoph Lameter <cl@gentwo.org>
Subject: Re: [PATCH] mm/damon: align MMU notifier range when clearing PMD young bit
Date: Fri, 23 Oct 2026 18:25:39 -0700	[thread overview]
Message-ID: <20261024012540.89397-1-sj@kernel.org> (raw)
In-Reply-To: <179273169185.2.1655708299473876346.damon-pmd-kvm-reply-draft@gmail.com>

On Fri, 23 Oct 2026 13:01:31 +0800 Aveline Noir <jm5905938@gmail.com> wrote:

> Hi SJ,
> 
> On Thu, 22 Oct 2026 17:20:17 -0700 SJ Park <sj@kernel.org> wrote:
> > I Cc-ed them.  Please Cc all
> > recipients who get_maitnainer.pl is recommending, from the next time.
> 
> Sorry for that. Maybe I will use b4 next time :)
> 
> > However, I think this patch explains its context very well, and therefore
> > this link is not needed.
> 
> Sure , That make sense.
> 
> > Were you also able to confirm the expected wrong behavior (missing part
> > of the sampled huge page and age secondary mapping), too?
> 
> Yes. A test with nested x86-64 KVM confirmed both effects. With
> 4 KiB EPT mappings, a midpoint PMD sample left the first 1 MiB young and
> aged the next THP's first 1 MiB. With 2 MiB EPT mappings, both whole THPs
> were aged. After the fix, only the sampled THP was aged in both cases.

Thank you for confirming!


Thanks,
SJ

[...]

      reply	other threads:[~2026-10-24  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 14:26 Aveline Noir
2026-10-23  0:20 ` SJ Park
2026-10-23  5:01   ` Aveline Noir
2026-10-24  1:25     ` 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=20261024012540.89397-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=cl@gentwo.org \
    --cc=damon@lists.linux.dev \
    --cc=foersleo@amazon.de \
    --cc=jm5905938@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sh@gentwo.org \
    --cc=shakeel.butt@linux.dev \
    --cc=shubhang@os.amperecomputing.com \
    --cc=sieberf@amazon.com \
    --cc=sjpark@amazon.de \
    /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®