From: SJ Park <sj@kernel.org>
To: Gutierrez Asier <gutierrez.asier@huawei-partners.com>
Cc: SJ Park <sj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
damon@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH REPOST 0/5] mm/damon/vaddr: support {prep,apply}_probes
Date: Wed, 9 Sep 2026 07:43:09 -0700 [thread overview]
Message-ID: <20260909144310.107006-1-sj@kernel.org> (raw)
In-Reply-To: <8f193651-9a6a-421b-91a7-df4a231786fd@huawei-partners.com>
On Wed, 9 Sep 2026 17:39:23 +0300 Gutierrez Asier <gutierrez.asier@huawei-partners.com> wrote:
[...]
> I was under the impression that with the change, all possible operations would
> have a prep_probes handler. I just noticed that we also have fvaddr, where
> ctx->ops.prep_probes is NULL.
>
> Ignore my comment :-)>
No worry, thank you for reviewing this :)
Thanks,
SJ
[...]
next prev parent reply other threads:[~2026-09-09 14:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 14:04 SJ Park
2026-09-09 14:04 ` [PATCH REPOST 1/5] mm/damon/vaddr: support prep_probes SJ Park
2026-09-11 1:59 ` Lian Wang
2026-09-09 14:04 ` [PATCH REPOST 2/5] mm/damon/paddr: move probe filter handling to ops-common SJ Park
2026-09-11 2:00 ` Lian Wang
2026-09-09 14:04 ` [PATCH REPOST 3/5] mm/damon/vaddr: support apply_probe SJ Park
2026-09-09 14:04 ` [PATCH REPOST 4/5] mm/damon/vaddr: extend apply_probes() for hugetlb SJ Park
2026-09-11 2:00 ` Lian Wang
2026-09-11 9:53 ` Kunwu Chan
2026-09-09 14:04 ` [PATCH REPOST 5/5] mm/damon/vaddr: support pgidle_unset probe filter type SJ Park
2026-09-11 2:01 ` Lian Wang
2026-09-11 13:33 ` SJ Park
2026-09-11 10:04 ` Kunwu Chan
2026-09-11 13:32 ` SJ Park
2026-09-11 15:32 ` KunWu Chan
2026-09-09 14:25 ` [PATCH REPOST 0/5] mm/damon/vaddr: support {prep,apply}_probes Gutierrez Asier
2026-09-09 14:31 ` SJ Park
2026-09-09 14:39 ` Gutierrez Asier
2026-09-09 14:43 ` SJ Park [this message]
2026-09-09 14:33 ` SJ Park
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=20260909144310.107006-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=damon@lists.linux.dev \
--cc=gutierrez.asier@huawei-partners.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 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®