From: SeongJae Park <sjpark@amazon.com>
To: Greg KH <greg@kroah.com>
Cc: SeongJae Park <sjpark@amazon.com>,
SeongJae Park <sjpark@amazon.de>, <Jonathan.Cameron@huawei.com>,
<aarcange@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <amit@kernel.org>,
<benh@kernel.crashing.org>, <brendan.d.gregg@gmail.com>,
<brendanhiggins@google.com>, <cai@lca.pw>,
<colin.king@canonical.com>, <corbet@lwn.net>, <david@redhat.com>,
<dwmw@amazon.com>, <elver@google.com>, <fan.du@intel.com>,
<foersleo@amazon.de>, <gthelen@google.com>, <irogers@google.com>,
<jolsa@redhat.com>, <kirill@shutemov.name>,
<mark.rutland@arm.com>, <mgorman@suse.de>, <minchan@kernel.org>,
<mingo@redhat.com>, <namhyung@kernel.org>, <peterz@infradead.org>,
<rdunlap@infradead.org>, <riel@surriel.com>,
<rientjes@google.com>, <rostedt@goodmis.org>, <rppt@kernel.org>,
<sblbir@amazon.com>, <shakeelb@google.com>, <shuah@kernel.org>,
<sj38.park@gmail.com>, <snu@amazon.de>, <vbabka@suse.cz>,
<vdavydov.dev@gmail.com>, <yang.shi@linux.alibaba.com>,
<ying.huang@intel.com>, <zgf574564920@gmail.com>,
<linux-damon@amazon.com>, <linux-mm@kvack.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v24 07/14] mm/damon: Implement a debugfs-based user space interface
Date: Fri, 5 Feb 2021 16:59:02 +0100 [thread overview]
Message-ID: <20210205155902.31102-1-sjpark@amazon.com> (raw)
In-Reply-To: <YB1kZaD/7omxXztF@kroah.com>
On Fri, 5 Feb 2021 16:29:41 +0100 Greg KH <greg@kroah.com> wrote:
> On Thu, Feb 04, 2021 at 04:31:43PM +0100, SeongJae Park wrote:
> > From: SeongJae Park <sjpark@amazon.de>
> >
> > DAMON is designed to be used by kernel space code such as the memory
> > management subsystems, and therefore it provides only kernel space API.
> > That said, letting the user space control DAMON could provide some
> > benefits to them. For example, it will allow user space to analyze
> > their specific workloads and make their own special optimizations.
> >
> > For such cases, this commit implements a simple DAMON application kernel
> > module, namely 'damon-dbgfs', which merely wraps the DAMON api and
> > exports those to the user space via the debugfs.
> >
> > 'damon-dbgfs' exports three files, ``attrs``, ``target_ids``, and
> > ``monitor_on`` under its debugfs directory, ``<debugfs>/damon/``.
[...]
> > ---
> > include/linux/damon.h | 3 +
> > mm/damon/Kconfig | 9 +
> > mm/damon/Makefile | 1 +
> > mm/damon/core.c | 47 +++++
> > mm/damon/dbgfs.c | 387 ++++++++++++++++++++++++++++++++++++++++++
> > 5 files changed, 447 insertions(+)
> > create mode 100644 mm/damon/dbgfs.c
[...]
> > diff --git a/mm/damon/dbgfs.c b/mm/damon/dbgfs.c
> > new file mode 100644
> > index 000000000000..db15380737d1
> > --- /dev/null
> > +++ b/mm/damon/dbgfs.c
[...]
> > +
> > +static int dbgfs_fill_ctx_dir(struct dentry *dir, struct damon_ctx *ctx)
> > +{
> > + const char * const file_names[] = {"attrs", "target_ids"};
> > + const struct file_operations *fops[] = {&attrs_fops, &target_ids_fops};
> > + int i;
> > +
> > + for (i = 0; i < ARRAY_SIZE(file_names); i++) {
> > + if (!debugfs_create_file(file_names[i], 0600, dir,
> > + ctx, fops[i])) {
> > + pr_err("failed to create %s file\n", file_names[i]);
> > + return -ENOMEM;
>
> No need to check the return value of this function, just keep going and
> ignore it as there's nothing to do and kernel code should not do
> different things based on the output of any debugfs calls.
>
> Also, this check is totally wrong and doesn't do what you think it is
> doing...
Ok, I will drop the check.
>
> > +static int __init __damon_dbgfs_init(void)
> > +{
> > + struct dentry *dbgfs_root;
> > + const char * const file_names[] = {"monitor_on"};
> > + const struct file_operations *fops[] = {&monitor_on_fops};
> > + int i;
> > +
> > + dbgfs_root = debugfs_create_dir("damon", NULL);
> > + if (IS_ERR(dbgfs_root)) {
> > + pr_err("failed to create the dbgfs dir\n");
> > + return PTR_ERR(dbgfs_root);
>
> Again, no need to check anything, just pass the result of a debugfs call
> back into another one just fine.
Ok.
>
> > + }
> > +
> > + for (i = 0; i < ARRAY_SIZE(file_names); i++) {
> > + if (!debugfs_create_file(file_names[i], 0600, dbgfs_root,
> > + NULL, fops[i])) {
>
> Again, this isn't checking what you think it is, so please don't do it.
Got it.
I will fix those as you suggested in the next version.
Thanks,
SeongJae Park
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2021-02-05 15:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 15:31 [PATCH v24 00/14] Subject: Introduce Data Access MONitor (DAMON) SeongJae Park
2021-02-04 15:31 ` [PATCH v24 01/14] mm: " SeongJae Park
2021-02-04 15:31 ` [PATCH v24 02/14] mm/damon/core: Implement region-based sampling SeongJae Park
2021-02-04 15:31 ` [PATCH v24 03/14] mm/damon: Adaptively adjust regions SeongJae Park
2021-02-04 15:31 ` [PATCH v24 04/14] mm/idle_page_tracking: Make PG_idle reusable SeongJae Park
2021-02-04 15:31 ` [PATCH v24 05/14] mm/damon: Implement primitives for the virtual memory address spaces SeongJae Park
2021-02-04 15:31 ` [PATCH v24 06/14] mm/damon: Add a tracepoint SeongJae Park
2021-02-04 15:31 ` [PATCH v24 07/14] mm/damon: Implement a debugfs-based user space interface SeongJae Park
2021-02-05 15:29 ` Greg KH
2021-02-05 15:59 ` SeongJae Park [this message]
2021-02-04 15:31 ` [PATCH v24 08/14] mm/damon/dbgfs: Implement recording feature SeongJae Park
2021-02-04 15:31 ` [PATCH v24 09/14] mm/damon/dbgfs: Export kdamond pid to the user space SeongJae Park
2021-02-04 15:31 ` [PATCH v24 10/14] mm/damon/dbgfs: Support multiple contexts SeongJae Park
2021-02-04 15:31 ` [PATCH v24 11/14] Documentation: Add documents for DAMON SeongJae Park
2021-02-24 7:49 ` SeongJae Park
2021-02-04 15:31 ` [PATCH v24 12/14] mm/damon: Add kunit tests SeongJae Park
2021-02-04 15:31 ` [PATCH v24 13/14] mm/damon: Add user space selftests SeongJae Park
2021-02-04 15:31 ` [PATCH v24 14/14] MAINTAINERS: Update for DAMON SeongJae Park
2021-02-24 13:30 ` [PATCH v24 00/14] Subject: Introduce Data Access MONitor (DAMON) SeongJae Park
2021-03-04 10:07 ` SeongJae 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=20210205155902.31102-1-sjpark@amazon.com \
--to=sjpark@amazon.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=aarcange@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amit@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=brendan.d.gregg@gmail.com \
--cc=brendanhiggins@google.com \
--cc=cai@lca.pw \
--cc=colin.king@canonical.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.com \
--cc=elver@google.com \
--cc=fan.du@intel.com \
--cc=foersleo@amazon.de \
--cc=greg@kroah.com \
--cc=gthelen@google.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=kirill@shutemov.name \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rdunlap@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=sblbir@amazon.com \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
--cc=snu@amazon.de \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.com \
--cc=zgf574564920@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox