On Tue, 31 Dec 2024 21:56:43 +0900 Akinobu Mita <akinobu.mita@xxxxxxxxx> wrote: > 2024年12月31日(火) 3:39 SeongJae Park <sj@xxxxxxxxxx>: > > > > On Mon, 30 Dec 2024 10:28:13 -0800 SeongJae Park <sj@xxxxxxxxxx> wrote: > > > > > Hello Akinobu, > > > > > > On Mon, 30 Dec 2024 22:42:20 +0900 Akinobu Mita <akinobu.mita@xxxxxxxxx> wrote: > > > > > > > Currently, the address ranges are displayed in decimal format in > > > > tracepoints for DAMON, but hexadecimal format is easier to compare with > > > > address ranges in /proc/<pid>/numa_maps. > > > > > > I agree that it could be easier for the use case. But, I think writing and > > > using a script converting formats for DAMON tracepoint output or numa_maps > > > could also be a way to resolve the issue. > > > > For example, we can extend 'damo' to optionally do the conversion. Depending > > on your use case (if you also use 'damo' for your use case), it might be a way > > to move forward? > > I'm currently using perf trace (-e damon:* --libtraceevent_print) to see which > address range accesses were detected or not, Thank you for kindly sharing your use case. I'm not very sure why you need to use 'perf trace' instead of 'damo', though. 'damo' supports recording the whole events and getting access monitoring result snapshots in live, with a few results filtering criterias. I just assume you had to use 'perf trace' since you want to read full events in realtime, but please let me know if you want to know more details about 'damo' features that might help you. > so as you suggested, I'll create a > script to convert the output of the perf trace. Thank you for accepting my suggestion. Please let me know if there is anything that I can help at writing the script. For example, if you really need to use 'perf trace', we're open to extend 'damo' for that. Thanks, SJ
