From: SJ Park <sj@kernel.org>
To: Enze Li <lienze@kylinos.cn>
Cc: SJ Park <sj@kernel.org>,
damon@lists.linux.dev, linux-mm@kvack.org, enze.li@gmx.com
Subject: Re: [PATCH] samples/damon/prcl: add module parameter description for target_pid
Date: Fri, 17 Jul 2026 07:23:47 -0700 [thread overview]
Message-ID: <20260717142348.27427-1-sj@kernel.org> (raw)
In-Reply-To: <875x2ej95p.fsf@kylinos.cn>
On Fri, 17 Jul 2026 16:46:26 +0800 Enze Li <lienze@kylinos.cn> wrote:
>
> Hi SJ,
>
> Thank you for your review.
>
> On Thu, Jul 16 2026 at 06:54:37 AM -0700, SJ Park wrote:
> > Hello Enze,
> >
> >
> > Thank you for this patch!
> >
> > On Thu, 16 Jul 2026 17:14:44 +0800 Enze Li <lienze@kylinos.cn> wrote:
> >
> >> Document 'target_pid' via MODULE_PARM_DESC so its meaning is visible
> >> through kernel command line usage and sysfs interface.
> >
> > But... It is a static module. Is there a way to read this documentation from
> > the user space? If there is no such a way, I don't really think this change is
> > needed. If we want to document this, we could use comments.
>
> AFAIK, MODULE_PARM_DESC() is for loadable modules. For builtins, it’s
> effectively just a comment.
Thank you for clarifying, Enze.
> That said, if DAMON gains loadable module
> support later, having these descriptors in place means we won’t need to
> touch the code. WDYT?
I think it is not too late to add MODULE_PARM_DESC() when we add loadable
modules support. As of now, no clear needs for loadable module support have
reported, though.
Thank,
SJ
[...]
next parent reply other threads:[~2026-07-17 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875x2ej95p.fsf@kylinos.cn>
2026-07-17 14:23 ` SJ Park [this message]
[not found] <20260716091444.284702-1-lienze@kylinos.cn>
2026-07-16 13:54 ` [PATCH] samples/damon/prcl: add module parameter description for target_pid 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=20260717142348.27427-1-sj@kernel.org \
--to=sj@kernel.org \
--cc=damon@lists.linux.dev \
--cc=enze.li@gmx.com \
--cc=lienze@kylinos.cn \
--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