DAMON: Support Access Monitoring of Any Address Space Including Physical Memory
Subsystems (6)
v4 cover DAMON: Support Access Monitoring of Any Address Space Including Physical Memory
From: SeongJae Park <[email protected]>
Currently, DAMON[1] supports only virtual memory address spaces because it utilizes PTE Accessed bits as its low-level access check primitive and ``struct vma`` as a way to address the monitoring target regions. However, the core idea of DAMON, which makes it able to provide the accurate, efficient, and scalable monitoring, is in a separate higher layer. Therefore, DAMON can be extended for other various address spaces by changing the two low primitives to others for the address spaces.
This patchset makes the DAMON's low level primitives configurable and provide reference implementation of the primitives for the virtual memory address spaces and the physical memory address space. Therefore, users can monitor both of the two address spaces by simply configuring the provided low level primitives. Note that only the user memory is supported, as same to the idle page access tracking feature.
After this patchset, the programming interface users can implement the primitives by themselves for their special use cases. Clean/dirty/entire page cache, NUMA nodes, specific files, or block devices would be examples of such special use cases.
[1] https://lore.kernel.org/linux-mm/[email protected]/
Baseline and Complete Git Trees
===============================
The patches are based on the v5.7 plus DAMON v15 patchset[1] and DAMOS RFC v11 patchset[2]. You can also clone the complete git tree:
$ git clone git://github.com/sjp38/linux -b cdamon/rfc/v3
The web is also available:
https://github.com/sjp38/linux/releases/tag/cdamon/rfc/v3
[1] https://lore.kernel.org/linux-mm/[email protected]/
[2] https://lore.kernel.org/linux-mm/[email protected]/
Sequence of Patches
===================
The sequence of patches is as follow. The 1st patch defines the monitoring region again based on pure address range abstraction so that no assumption of virtual memory is in there.
The 2nd patch allows users to configure the low level pritimives for initialization and dynamic update of the target address regions, which were previously coupled with the virtual memory. Then, the 3rd and 4th patches allow user space to also be able to set the monitoring target regions via the debugfs and the user space tool. The 5th patch documents this feature.
The 6th patch makes the access check primitives, which were coupled with the virtual memory address, freely configurable. Now any address space can be supported. The 7th patch provides the reference implementations of the configurable primitives for the physical memory monitoring. The 8th and 9th patch makes the user space to be able to use the physical memory monitoring via debugfs and the user space tool, respectively. Finally, the 10th patch documents the physical memory monitoring support.
Patch History
=============
Changes from RFC v2
(https://lore.kernel.org/linux-mm/[email protected]/)
- Support the physical memory monitoring with the user space tool
- Use 'pfn_to_online_page()' (David Hildenbrand)
- Document more detail on random 'pfn' and its safeness (David Hildenbrand)
Changes from RFC v1
(https://lore.kernel.org/linux-mm/[email protected]/)
- Provide the reference primitive implementations for the physical memory
- Connect the extensions with the debugfs interface
SeongJae Park (8):
mm/damon/debugfs: Allow users to set initial monitoring target regions tools/damon: Implement init target regions feature Docs/damon: Document 'initial_regions' feature
mm/rmap: Export essential functions for rmap_run
mm/damon: Implement callbacks for physical memory monitoring mm/damon/debugfs: Support physical memory monitoring tools/damon/record: Support physical memory address spce Docs/damon: Document physical memory monitoring support
Documentation/admin-guide/mm/damon/faq.rst | 7 +- Documentation/admin-guide/mm/damon/index.rst | 1 - Documentation/admin-guide/mm/damon/plans.rst | 7 - Documentation/admin-guide/mm/damon/usage.rst | 73 +++- include/linux/damon.h | 5 + mm/damon.c | 374 ++++++++++++++++++- mm/rmap.c | 2 + mm/util.c | 1 + tools/damon/_damon.py | 41 ++ tools/damon/heats.py | 2 +- tools/damon/record.py | 41 +- tools/damon/schemes.py | 12 +- 12 files changed, 532 insertions(+), 34 deletions(-) delete mode 100644 Documentation/admin-guide/mm/damon/plans.rst
Signature · 1 line
2.17.1
RFC v4 1/8 mm/damon/debugfs: Allow users to set initial monitoring target regions
From: SeongJae Park <[email protected]>
Some users would want to monitor only a part of the entire virtual memory address space. The '->init_target_regions' callback is therefore provided, but only programming interface can use it.
For the reason, this commit introduces a new debugfs file, 'init_region'. Users can specify which initial monitoring target address regions they want by writing special input to the file. The input should describe each region in each line in below form:
<pid> <start address> <end address>
This commit also makes the default '->init_target_regions' callback, 'kdamon_init_vm_regions()' to do nothing if the user has set the initial target regions already.
Note that the regions will be updated to cover entire memory mapped regions after 'regions update interval'. If you want the regions to not be updated after the initial setting, you could set the interval as a very long time, say, a few decades.
--- mm/damon.c | 156 +++++++++++++++++++++++++++++++++++++++++++++++++++-- 1 file changed, 152 insertions(+), 4 deletions(-)
mm/damon.c +152 -4
@@ -1790,6 +1790,147 @@ static ssize_t debugfs_record_write(struct file *file,return ret; } +static ssize_t sprint_init_regions (struct damon_ctx *c,char *buf,ssize_t len) +{ +struct damon_task *t; +struct damon_region *r; +int written =0 ; +int rc; + +damon_for_each_task (t, c) { +damon_for_each_region (r, t) { + rc =snprintf (&buf[written], len - written, +"%d %lu %lu\n" , + t->pid, r->ar.start, r->ar.end); +if (!rc) +return -ENOMEM ; + written += rc; + } + } +return written; +} + +static ssize_t debugfs_init_regions_read (struct file *file,char __user *buf, +size_t count,loff_t *ppos) +{ +struct damon_ctx *ctx = &damon_user_ctx; +char *kbuf; +ssize_t len; + + kbuf =kmalloc (count,GFP_KERNEL ); +if (!kbuf) +return -ENOMEM ; + +mutex_lock (&ctx->kdamond_lock); +if (ctx->kdamond) { +mutex_unlock (&ctx->kdamond_lock); +return -EBUSY ; + } + + len =sprint_init_regions (ctx, kbuf, count); +mutex_unlock (&ctx->kdamond_lock); +if (len <0 ) + goto out; + len =simple_read_from_buffer (buf, count, ppos, kbuf, len); + +out: +kfree (kbuf); +return len; +} + +static int add_init_region (struct damon_ctx *c, +int pid,struct damon_addr_range *ar) +{ +struct damon_task *t; +struct damon_region *r, *prev; +int rc = -EINVAL ; + +if (ar->start >= ar->end) +return -EINVAL ; + +damon_for_each_task (t, c) { +if (t->pid == pid) { + r =damon_new_region (c, ar->start, ar->end); +if (!r) +return -ENOMEM ; +damon_add_region (r, t); +if (nr_damon_regions (t) >1 ) { + prev =damon_prev_region (r); +if (prev->ar.end > r->ar.start) { +damon_destroy_region (r); +return -EINVAL ; + } + } + rc =0 ; + } + } +return rc; +} + +static int set_init_regions (struct damon_ctx *c,const char *str,ssize_t len) +{ +struct damon_task *t; +struct damon_region *r, *next; +int pos =0 , parsed, ret; +int pid; +struct damon_addr_range ar; +int err; + +damon_for_each_task (t, c) { +damon_for_each_region_safe (r, next, t) +damon_destroy_region (r); + } + +while (pos < len) { + ret =sscanf (&str[pos],"%d %lu %lu%n" , + &pid, &ar.start, &ar.end, &parsed); +if (ret !=3 ) +break ; + err =add_init_region (c, pid, &ar); +if (err) + goto fail; + pos += parsed; + } + +return 0 ; + +fail: +damon_for_each_task (t, c) { +damon_for_each_region_safe (r, next, t) +damon_destroy_region (r); + } +return err; +} + +static ssize_t debugfs_init_regions_write (struct file *file, +const char __user *buf,size_t count, +loff_t *ppos) +{ +struct damon_ctx *ctx = &damon_user_ctx; +char *kbuf; +ssize_t ret = count; +int err; + + kbuf =user_input_str (buf, count, ppos); +if (IS_ERR (kbuf)) +return PTR_ERR (kbuf); + +mutex_lock (&ctx->kdamond_lock); +if (ctx->kdamond) { + ret = -EBUSY ; + goto unlock_out; + } + + err =set_init_regions (ctx, kbuf, ret); +if (err) + ret = err; + +unlock_out: +mutex_unlock (&ctx->kdamond_lock); +kfree (kbuf); +return ret; +} +static ssize_t debugfs_attrs_read (struct file *file,char __user *buf,size_t count,loff_t *ppos) {
@@ -1866,6 +2007,12 @@ static const struct file_operations record_fops = { .write = debugfs_record_write, }; +static const struct file_operations init_regions_fops = { + .owner =THIS_MODULE , + .read = debugfs_init_regions_read, + .write = debugfs_init_regions_write, +}; +static const struct file_operations attrs_fops = { .owner =THIS_MODULE , .read = debugfs_attrs_read,
@@ -1876,10 +2023,11 @@ static struct dentry *debugfs_root;static int __init damon_debugfs_init (void ) { -const char *const file_names[] = {"attrs" ,"record" ,"schemes" , -"pids" ,"monitor_on" }; -const struct file_operations *fops[] = {&attrs_fops, &record_fops, - &schemes_fops, &pids_fops, &monitor_on_fops}; +const char *const file_names[] = {"attrs" ,"init_regions" ,"record" , +"schemes" ,"pids" ,"monitor_on" }; +const struct file_operations *fops[] = {&attrs_fops, + &init_regions_fops, &record_fops, &schemes_fops, &pids_fops, + &monitor_on_fops};int i; debugfs_root =debugfs_create_dir ("damon" ,NULL );
Signature · 1 line
2.17.1
RFC v4 2/8 tools/damon: Implement init target regions feature
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit updates the damon user space tool to support the initial monitoring target regions feature.
--- tools/damon/_damon.py | 39 +++++++++++++++++++++++++++++++++++++++ tools/damon/record.py | 12 +++++++----- tools/damon/schemes.py | 12 +++++++----- 3 files changed, 53 insertions(+), 10 deletions(-)
tools/damon/_damon.py +39 -0
@@ -12,12 +12,25 @@ debugfs_attrs = None debugfs_record = None debugfs_schemes = None debugfs_pids = None +debugfs_init_regions = None debugfs_monitor_on = None def set_target_pid(pid): return subprocess.call('echo %s > %s' % (pid, debugfs_pids), shell=True, executable='/bin/bash') +def set_target(pid, init_regions=[]): + rc = set_target_pid(pid) + if rc: + return rc + + if not os.path.exists(debugfs_init_regions): + return 0 + + string = ' '.join(['%s %d %d' % (pid, r[0], r[1]) for r in init_regions]) + return subprocess.call('echo "%s" > %s' % (string, debugfs_init_regions), + shell=True, executable='/bin/bash') + def turn_damon(on_off): return subprocess.call("echo %s > %s" % (on_off, debugfs_monitor_on), shell=True, executable="/bin/bash")
@@ -97,6 +110,7 @@ def chk_update_debugfs(debugfs): global debugfs_record global debugfs_schemes global debugfs_pids + global debugfs_init_regions global debugfs_monitor_on debugfs_damon = os.path.join(debugfs, 'damon')
@@ -104,6 +118,7 @@ def chk_update_debugfs(debugfs): debugfs_record = os.path.join(debugfs_damon, 'record') debugfs_schemes = os.path.join(debugfs_damon, 'schemes') debugfs_pids = os.path.join(debugfs_damon, 'pids') + debugfs_init_regions = os.path.join(debugfs_damon, 'init_regions') debugfs_monitor_on = os.path.join(debugfs_damon, 'monitor_on') if not os.path.isdir(debugfs_damon):
@@ -131,6 +146,26 @@ def cmd_args_to_attrs(args): return Attrs(sample_interval, aggr_interval, regions_update_interval, min_nr_regions, max_nr_regions, rbuf_len, rfile_path, schemes) +def cmd_args_to_init_regions(args): + regions = [] + for arg in args.regions.split(): + addrs = arg.split('-') + try: + if len(addrs) != 2: + raise Exception('two addresses not given') + start = int(addrs[0]) + end = int(addrs[1]) + if start >= end: + raise Exception('start >= end') + if regions and regions[-1][1] > start: + raise Exception('regions overlap') + except Exception as e: + print('Wrong \'--regions\' argument (%s)' % e) + exit(1) + + regions.append([start, end]) + return regions + def set_attrs_argparser(parser): parser.add_argument('-d', '--debugfs', metavar='<debugfs>', type=str, default='/sys/kernel/debug', help='debugfs mounted path')
@@ -144,3 +179,7 @@ def set_attrs_argparser(parser): default=10, help='minimal number of regions') parser.add_argument('-m', '--maxr', metavar='<# regions>', type=int, default=1000, help='maximum number of regions') + +def set_init_regions_argparser(parser): + parser.add_argument('-r', '--regions', metavar='"<start>-<end> ..."', + type=str, default='', help='monitoring target address regions')
tools/damon/record.py +7 -5
@@ -13,7 +13,7 @@ import time import _damon -def do_record(target, is_target_cmd, attrs, old_attrs): +def do_record(target, is_target_cmd, init_regions, attrs, old_attrs): if os.path.isfile(attrs.rfile_path): os.rename(attrs.rfile_path, attrs.rfile_path + '.old')
@@ -24,8 +24,8 @@ def do_record(target, is_target_cmd, attrs, old_attrs): if is_target_cmd: p = subprocess.Popen(target, shell=True, executable='/bin/bash') target = p.pid - if _damon.set_target_pid(target): - print('pid setting (%s) failed' % target) + if _damon.set_target(target, init_regions): + print('target setting (%s, %s) failed' % (target, init_regions)) cleanup_exit(old_attrs, -2) if _damon.turn_damon('on'): print('could not turn on damon' % target)
@@ -65,6 +65,7 @@ def chk_permission(): def set_argparser(parser): _damon.set_attrs_argparser(parser) + _damon.set_init_regions_argparser(parser) parser.add_argument('target', type=str, metavar='<target>', help='the target command or the pid to record') parser.add_argument('-l', '--rbuf', metavar='<len>', type=int,
@@ -88,19 +89,20 @@ def main(args=None): args.schemes = '' new_attrs = _damon.cmd_args_to_attrs(args) + init_regions = _damon.cmd_args_to_init_regions(args) target = args.target target_fields = target.split() if not subprocess.call('which %s > /dev/null' % target_fields[0], shell=True, executable='/bin/bash'): - do_record(target, True, new_attrs, orig_attrs) + do_record(target, True, init_regions, new_attrs, orig_attrs) else: try: pid = int(target) except: print('target \'%s\' is neither a command, nor a pid' % target) exit(1) - do_record(target, False, new_attrs, orig_attrs) + do_record(target, False, init_regions, new_attrs, orig_attrs) if __name__ == '__main__': main()
tools/damon/schemes.py +7 -5
@@ -14,7 +14,7 @@ import time import _convert_damos import _damon -def run_damon(target, is_target_cmd, attrs, old_attrs): +def run_damon(target, is_target_cmd, init_regions, attrs, old_attrs): if os.path.isfile(attrs.rfile_path): os.rename(attrs.rfile_path, attrs.rfile_path + '.old')
@@ -27,8 +27,8 @@ def run_damon(target, is_target_cmd, attrs, old_attrs): if is_target_cmd: p = subprocess.Popen(target, shell=True, executable='/bin/bash') target = p.pid - if _damon.set_target_pid(target): - print('pid setting (%s) failed' % target) + if _damon.set_target(target, init_regions): + print('target setting (%s, %s) failed' % (target, init_regions)) cleanup_exit(old_attrs, -2) if _damon.turn_damon('on'): print('could not turn on damon' % target)
@@ -67,6 +67,7 @@ def chk_permission(): def set_argparser(parser): _damon.set_attrs_argparser(parser) + _damon.set_init_regions_argparser(parser) parser.add_argument('target', type=str, metavar='<target>', help='the target command or the pid to record') parser.add_argument('-c', '--schemes', metavar='<file>', type=str,
@@ -91,19 +92,20 @@ def main(args=None): args.out = 'null' args.schemes = _convert_damos.convert(args.schemes, args.sample, args.aggr) new_attrs = _damon.cmd_args_to_attrs(args) + init_regions = _damon.cmd_args_to_init_regions(args) target = args.target target_fields = target.split() if not subprocess.call('which %s > /dev/null' % target_fields[0], shell=True, executable='/bin/bash'): - run_damon(target, True, new_attrs, orig_attrs) + run_damon(target, True, init_regions, new_attrs, orig_attrs) else: try: pid = int(target) except: print('target \'%s\' is neither a command, nor a pid' % target) exit(1) - run_damon(target, False, new_attrs, orig_attrs) + run_damon(target, False, init_regions, new_attrs, orig_attrs) if __name__ == '__main__': main()
Signature · 1 line
2.17.1
RFC v4 3/8 Docs/damon: Document 'initial_regions' feature
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit documents the 'initial_regions' feature.
--- Documentation/admin-guide/mm/damon/usage.rst | 34 ++++++++++++++++++++ 1 file changed, 34 insertions(+)
Documentation/admin-guide/mm/damon/usage.rst +34 -0
@@ -329,6 +329,40 @@ having pids 42 and 4242 as the processes to be monitored and check it again:: Note that setting the pids doesn't start the monitoring. +Initial Monitoring Target Regions +--------------------------------- + +DAMON automatically sets and updates the monitoring target regions so that +entire memory mappings of target processes can be covered. However, users +might want to limit the monitoring region to specific address ranges, such as +the heap, the stack, or specific file-mapped area. Or, some users might know +the initial access pattern of their workloads and therefore want to set optimal +initial regions for the 'adaptive regions adjustment'. + +In such cases, users can explicitly set the initial monitoring target regions +as they want, by writing proper values to the ``init_regions`` file. Each line +of the input should represent one region in below form.:: + + <pid> <start address> <end address> + +The ``pid`` should be already in ``pids`` file, and the regions should be +passed in address order. For example, below commands will set a couple of +address ranges, ``1-100`` and ``100-200`` as the initial monitoring target +region of process 42, and another couple of address ranges, ``20-40`` and +``50-100`` as that of process 4242.:: + + # cd <debugfs>/damon + # echo "42 1 100 + 42 100 200 + 4242 20 40 + 4242 50 100" > init_regions + +Note that this sets the initial monitoring target regions only. DAMON will +automatically updates the boundary of the regions after one ``regions update +interval``. Therefore, users should set the ``regions update interval`` large +enough. + + Record ------
Signature · 1 line
2.17.1
RFC v4 4/8 mm/rmap: Export essential functions for rmap_run
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit exports the three essential functions for ramp walk, 'page_lock_anon_vma_read()', 'rmap_walk()', and 'page_rmapping()', to GPL modules. Those will be used by DAMON for the physical memory address based access monitoring in the following commit.
--- mm/rmap.c | 2 ++ mm/util.c | 1 + 2 files changed, 3 insertions(+)
mm/rmap.c +2 -0
@@ -579,6 +579,7 @@ struct anon_vma *page_lock_anon_vma_read(struct page *page)rcu_read_unlock ();return anon_vma; } +EXPORT_SYMBOL_GPL (page_lock_anon_vma_read);void page_unlock_anon_vma_read (struct anon_vma *anon_vma) {
@@ -1934,6 +1935,7 @@ void rmap_walk(struct page *page, struct rmap_walk_control *rwc)else rmap_walk_file (page, rwc, false); } +EXPORT_SYMBOL_GPL (rmap_walk);/* Like rmap_walk, but caller holds relevant rmap lock */ void rmap_walk_locked (struct page *page,struct rmap_walk_control *rwc)
mm/util.c +1 -0
@@ -620,6 +620,7 @@ void *page_rmapping(struct page *page) page =compound_head (page);return __page_rmapping (page); } +EXPORT_SYMBOL_GPL (page_rmapping);/* * Return true if this page is mapped into pagetables.
Signature · 1 line
2.17.1
RFC v4 5/8 mm/damon: Implement callbacks for physical memory monitoring
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit implements the four callbacks (->init_target_regions, ->update_target_regions, ->prepare_access_check, and ->check_accesses) for the basic access monitoring of the physical memory address space. By setting the callback pointers to point those, users can easily monitor the accesses to the physical memory.
Internally, it uses the PTE Accessed bit, as similar to that of the virtual memory support. Also, it supports only user memory pages, as idle page tracking also does, for the same reason. If the monitoring target physical memory address range contains non-user memory pages, access check of the pages will do nothing but simply treat the pages as not accessed.
Users who want to use other access check primitives and/or monitor the non-user memory regions could implement and use their own callbacks.
--- include/linux/damon.h | 5 ++ mm/damon.c | 201 ++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 206 insertions(+)
include/linux/damon.h +5 -0
@@ -227,6 +227,11 @@ void kdamond_update_vm_regions(struct damon_ctx *ctx);void kdamond_prepare_vm_access_checks (struct damon_ctx *ctx);unsigned int kdamond_check_vm_accesses (struct damon_ctx *ctx); +void kdamond_init_phys_regions (struct damon_ctx *ctx); +void kdamond_update_phys_regions (struct damon_ctx *ctx); +void kdamond_prepare_phys_access_checks (struct damon_ctx *ctx); +unsigned int kdamond_check_phys_accesses (struct damon_ctx *ctx); +int damon_set_pids (struct damon_ctx *ctx,int *pids,ssize_t nr_pids); int damon_set_attrs(struct damon_ctx *ctx, unsigned long sample_int, unsigned long aggr_int, unsigned long regions_update_int,
mm/damon.c +201 -0
229 lines not on this page · raw message
Signature · 1 line
2.17.1
RFC v4 6/8 mm/damon/debugfs: Support physical memory monitoring
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit makes the debugfs interface to support the physical memory monitoring, in addition to the virtual memory monitoring.
Users can do the physical memory monitoring by writing a special keyword, 'paddr\n' to the 'pids' debugfs file. Then, DAMON will check the special keyword and configure the callbacks of the monitoring context for the debugfs user for physical memory. This will internally add one fake monitoring target process, which has pid as -1.
Unlike the virtual memory monitoring, DAMON debugfs will not automatically set the monitoring target region. Therefore, users should also set the monitoring target address region using the 'init_regions' debugfs file. While doing this, the 'pid' in the input should be '-1'.
Finally, the physical memory monitoring will not automatically terminated because it has fake monitoring target process. The user should explicitly turn off the monitoring by writing 'off' to the 'monitor_on' debugfs file.
--- mm/damon.c | 17 +++++++++++++++++ 1 file changed, 17 insertions(+)
mm/damon.c +17 -0
@@ -1918,6 +1918,23 @@ static ssize_t debugfs_pids_write(struct file *file,if (IS_ERR (kbuf))return PTR_ERR (kbuf); +if (!strncmp (kbuf,"paddr\n" , count)) { +/* Configure the context for physical memory monitoring */ + ctx->init_target_regions = kdamond_init_phys_regions; + ctx->update_target_regions = kdamond_update_phys_regions; + ctx->prepare_access_checks = kdamond_prepare_phys_access_checks; + ctx->check_accesses = kdamond_check_phys_accesses; + +/* Set the fake target task pid as -1 */ +snprintf (kbuf, count,"-1 " ); + }else { +/* Configure the context for virtual memory monitoring */ + ctx->init_target_regions = kdamond_init_vm_regions; + ctx->update_target_regions = kdamond_update_vm_regions; + ctx->prepare_access_checks = kdamond_prepare_vm_access_checks; + ctx->check_accesses = kdamond_check_vm_accesses; + } + targets =str_to_pids (kbuf, ret, &nr_targets);if (!targets) { ret = -ENOMEM ;
Signature · 1 line
2.17.1
RFC v4 7/8 tools/damon/record: Support physical memory address spce
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit allows users to record the data accesses on physical memory address space by passing 'paddr' as target to 'damo-record'. If the init regions are given, the regions will be monitored. Else, it will monitor biggest conitguous 'System RAM' region in '/proc/iomem' and monitor the region.
--- tools/damon/_damon.py | 2 ++ tools/damon/heats.py | 2 +- tools/damon/record.py | 29 ++++++++++++++++++++++++++++- 3 files changed, 31 insertions(+), 2 deletions(-)
tools/damon/_damon.py +2 -0
@@ -27,6 +27,8 @@ def set_target(pid, init_regions=[]): if not os.path.exists(debugfs_init_regions): return 0 + if pid == 'paddr': + pid = -1 string = ' '.join(['%s %d %d' % (pid, r[0], r[1]) for r in init_regions]) return subprocess.call('echo "%s" > %s' % (string, debugfs_init_regions), shell=True, executable='/bin/bash')
tools/damon/heats.py +1 -1
@@ -307,7 +307,7 @@ def plot_heatmap(data_file, output_file): set xrange [0:]; set yrange [0:]; set xlabel 'Time (ns)'; - set ylabel 'Virtual Address (bytes)'; + set ylabel 'Address (bytes)'; plot '%s' using 1:2:3 with image;""" % (terminal, output_file, data_file) subprocess.call(['gnuplot', '-e', gnuplot_cmd]) os.remove(data_file)
tools/damon/record.py +28 -1
@@ -73,6 +73,29 @@ def set_argparser(parser): parser.add_argument('-o', '--out', metavar='<file path>', type=str, default='damon.data', help='output file path') +def default_paddr_region(): + "Largest System RAM region becomes the default" + ret = [] + with open('/proc/iomem', 'r') as f: + # example of the line: '100000000-42b201fff : System RAM' + for line in f: + fields = line.split(':') + if len(fields) != 2: + continue + name = fields[1].strip() + if name != 'System RAM': + continue + addrs = fields[0].split('-') + if len(addrs) != 2: + continue + start = int(addrs[0], 16) + end = int(addrs[1], 16) + + sz_region = end - start + if not ret or sz_region > (ret[1] - ret[0]): + ret = [start, end] + return ret + def main(args=None): global orig_attrs if not args:
@@ -93,7 +116,11 @@ def main(args=None): target = args.target target_fields = target.split() - if not subprocess.call('which %s > /dev/null' % target_fields[0], + if target == 'paddr': # physical memory address space + if not init_regions: + init_regions = [default_paddr_region()] + do_record(target, False, init_regions, new_attrs, orig_attrs) + elif not subprocess.call('which %s > /dev/null' % target_fields[0], shell=True, executable='/bin/bash'): do_record(target, True, init_regions, new_attrs, orig_attrs) else:
Signature · 1 line
2.17.1
RFC v4 8/8 Docs/damon: Document physical memory monitoring support
In reply to SeongJae ParkFrom: SeongJae Park <[email protected]>
This commit adds description for the physical memory monitoring usage in the DAMON document.
--- Documentation/admin-guide/mm/damon/faq.rst | 7 +-- Documentation/admin-guide/mm/damon/index.rst | 1 - Documentation/admin-guide/mm/damon/plans.rst | 7 --- Documentation/admin-guide/mm/damon/usage.rst | 59 ++++++++++++++------ 4 files changed, 46 insertions(+), 28 deletions(-) delete mode 100644 Documentation/admin-guide/mm/damon/plans.rst
Documentation/admin-guide/mm/damon/faq.rst +3 -4
@@ -45,10 +45,9 @@ constructions and actual access checks can be implemented and configured on the DAMON core by the users. In this way, DAMON users can monitor any address space with any access check technique. -Nonetheless, DAMON provides a vma tracking and PTE Accessed bit check based -implementation of the address space dependent functions for the virtual memory -by default, for a reference and convenient use. In near future, we will also -provide that for physical memory address space. +Nonetheless, DAMON provides vma/rmap tracking and PTE Accessed bit check based +implementations of the address space dependent functions for the virtual memory +and the physical memory by default, for a reference and convenient use. Can I simply monitor page granularity?
Documentation/admin-guide/mm/damon/index.rst +0 -1
@@ -33,4 +33,3 @@ optimizations of their systems. faq mechanisms eval - plans
Documentation/admin-guide/mm/damon/plans.rst deleted +0 -7
@@ -1,7 +0,0 @@ -.. SPDX-License-Identifier: GPL-2.0 - -============ -Future Plans -============ - -TBD.
Documentation/admin-guide/mm/damon/usage.rst +43 -16
95 lines not on this page · raw message
Signature · 1 line
2.17.1
Sorry, the cover letter for previous version of the patchset was mistakenly sent. Below is the proper coverletter for this version.
================================ >8 ===========================================
Subject: [RFC v4 0/8] DAMON: Support Physical Memory Address Space Monitoring
DAMON[1] programming interface users can extend DAMON for any address space by implementing and using their own address-space specific low level primitives. However, the user space users who rely on the debugfs interface and user space tool, can monitor the virtual address space only. This is mainly due to DAMON is providing the reference implementation of the low level primitives for the virtual address space only.
This patchset implements another reference implementation of the low level primitives for the physical memory address space. Therefore, users can monitor both of the virtual and the physical address spaces by simply configuring the
provided low level primitives. Further, this patchset links the
implementation to the debugfs interface and the user space tool, so that user space users can also use the features.
Note that the implementation supports only the user memory, as same to the idle page access tracking feature.
[1] https://lore.kernel.org/linux-mm/[email protected]/
Baseline and Complete Git Trees
===============================
The patches are based on the v5.7 plus DAMON v16 patchset[1] and DAMOS RFC v12 patchset[2]. You can also clone the complete git tree:
$ git clone git://github.com/sjp38/linux -b cdamon/rfc/v4
The web is also available:
https://github.com/sjp38/linux/releases/tag/cdamon/rfc/v4
[1] https://lore.kernel.org/linux-mm/[email protected]/
[2] https://lore.kernel.org/linux-mm/[email protected]/
Sequence of Patches
===================
The sequence of patches is as follow.
The 1st and 2nd patches allow the debugfs interface and the user space tool to be able to set the monitoring target regions as they want, respectively. The 3rd patch documents the feature.
The 4th patch exports rmap essential functions to GPL modules as those are required from the DAMON's reference implementation of the low level primitives for the physical memory address space. The 5th patch provides the reference implementations of the configurable primitives for the physical memory monitoring. The 6th and 7th patches make the user space to be able to use the physical memory monitoring via debugfs and the user space tool, respectively. Finally, the 8th patch documents the physical memory monitoring support.
Patch History
=============
Changes from RFC v3
(https://lore.kernel.org/linux-mm/[email protected]/)
- Export rmap functions
- Reorganize for physical memory monitoring support only
- Clean up debugfs code
Changes from RFC v2
(https://lore.kernel.org/linux-mm/[email protected]/)
- Support the physical memory monitoring with the user space tool
- Use 'pfn_to_online_page()' (David Hildenbrand)
- Document more detail on random 'pfn' and its safeness (David Hildenbrand)
Changes from RFC v1
(https://lore.kernel.org/linux-mm/[email protected]/)
- Provide the reference primitive implementations for the physical memory
- Connect the extensions with the debugfs interface
SeongJae Park (8):
mm/damon/debugfs: Allow users to set initial monitoring target regions tools/damon: Implement init target regions feature Docs/damon: Document 'initial_regions' feature
mm/rmap: Export essential functions for rmap_run
mm/damon: Implement callbacks for physical memory monitoring mm/damon/debugfs: Support physical memory monitoring tools/damon/record: Support physical memory address spce Docs/damon: Document physical memory monitoring support
Documentation/admin-guide/mm/damon/faq.rst | 7 +- Documentation/admin-guide/mm/damon/index.rst | 1 - Documentation/admin-guide/mm/damon/plans.rst | 7 - Documentation/admin-guide/mm/damon/usage.rst | 73 +++- include/linux/damon.h | 5 + mm/damon.c | 374 ++++++++++++++++++- mm/rmap.c | 2 + mm/util.c | 1 + tools/damon/_damon.py | 41 ++ tools/damon/heats.py | 2 +- tools/damon/record.py | 41 +- tools/damon/schemes.py | 12 +- 12 files changed, 532 insertions(+), 34 deletions(-) delete mode 100644 Documentation/admin-guide/mm/damon/plans.rst
Signature · 1 line
2.17.1