awslabs/damo

option --numa_node 0 fails and default to the largest region

simini opened this issue · 1 comments

When trying to run with paddr targetting the NUMA node with ID=0, the code is treating numa_node=0 as numa_node=false here:
https://github.com/awslabs/damo/blob/next/record.py#L164
Hence tracing this area is not possible (unless you are lucky and it matches the default region).

Thank you so much for this report! I fixed this with damonitor@56aa308