[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201015152226.7106-1-sjpark@amazon.com>
Date: Thu, 15 Oct 2020 17:22:26 +0200
From: SeongJae Park <sjpark@...zon.com>
To: SeongJae Park <sjpark@...zon.com>
CC: <akpm@...ux-foundation.org>, <Jonathan.Cameron@...wei.com>,
<aarcange@...hat.com>, <acme@...nel.org>,
<alexander.shishkin@...ux.intel.com>, <amit@...nel.org>,
<benh@...nel.crashing.org>, <brendan.d.gregg@...il.com>,
<brendanhiggins@...gle.com>, <cai@....pw>,
<colin.king@...onical.com>, <corbet@....net>, <david@...hat.com>,
<dwmw@...zon.com>, <elver@...gle.com>, <fan.du@...el.com>,
<foersleo@...zon.de>, <gthelen@...gle.com>, <irogers@...gle.com>,
<jolsa@...hat.com>, <kirill@...temov.name>, <mark.rutland@....com>,
<mgorman@...e.de>, <minchan@...nel.org>, <mingo@...hat.com>,
<namhyung@...nel.org>, <peterz@...radead.org>,
<rdunlap@...radead.org>, <riel@...riel.com>, <rientjes@...gle.com>,
<rostedt@...dmis.org>, <rppt@...nel.org>, <sblbir@...zon.com>,
<shakeelb@...gle.com>, <shuah@...nel.org>, <sj38.park@...il.com>,
<snu@...zon.de>, <vbabka@...e.cz>, <vdavydov.dev@...il.com>,
<yang.shi@...ux.alibaba.com>, <ying.huang@...el.com>,
<zgf574564920@...il.com>, <linux-damon@...zon.com>,
<linux-mm@...ck.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v21 10/18] mm/damon: Implement a debugfs-based user space interface
On Mon, 5 Oct 2020 12:55:14 +0200 SeongJae Park <sjpark@...zon.com> wrote:
> From: SeongJae Park <sjpark@...zon.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.
[...]
> +
> +static ssize_t dbgfs_monitor_on_write(struct file *file,
> + const char __user *buf, size_t count, loff_t *ppos)
> +{
> + ssize_t ret = count;
> + char *kbuf;
> + int err;
> +
> + kbuf = user_input_str(buf, count, ppos);
> + if (IS_ERR(kbuf))
> + return PTR_ERR(kbuf);
> +
> + /* Remove white space */
> + if (sscanf(kbuf, "%s", kbuf) != 1)
> + return -EINVAL;
> + if (!strncmp(kbuf, "on", count))
> + err = dbgfs_start_ctxs(dbgfs_ctxs, dbgfs_nr_ctxs);
> + else if (!strncmp(kbuf, "off", count))
> + err = damon_stop(dbgfs_ctxs, dbgfs_nr_ctxs);
> + else
> + return -EINVAL;
> +
> + if (err)
> + ret = err;
> + return ret;
'kbuf' should be freed before returning from this function. I will fix it in
the next version. To find more potential memory leaks, I ran 'kmemleak' after
a set of correctness tests[1], but it didn't find more leaks.
[1] https://github.com/awslabs/damon-tests/tree/master/corr
Thanks,
SeongJae Park
Powered by blists - more mailing lists