- Test --numa_node 0 case
- damo show features implementation
  - collapse by time
  - Implement min/max snapshot format keyword
- damo reclaim: add a command for basic investigation
  - helps ensure DAMON_RECLAIM is working as expected
  - helps reporting issue
- Handle _damon_sysfs file i/o error for unsupported kernel features and
  conflicts with concurrent ones
- Optimize 'replay' performance
  - An approach for 2 MiB-granularity page management didn't show improvement
  - Optionally use C program like 'masim'
- Let 'replay' further parse vmas and alloc/release memory
- Unify wss and footprints report types
- Fixup 'damo show' on schemes_tried_regions unsupported kernels
  - Either make the warning clear, or support it using trace points
  - (https://github.com/awslabs/damo/issues/101)
- 'diagnose' command
  - check if nr_regions in bound
  - check if DAMOS quota is in control
- 'damo monitor'
  - add option to add snapshot as (optional) alternate of heatmap
- Show temperature histogram on holistic report
- heatmap: Support interactive zoom in/out/scrolling
- Provide virtual memory mapping information
  - shows when what virtual address has mappend and unmapped
- Implement an official feature to check if 'damo' supports the system
  - 'damo diagnose --kernel_support'?  Or, 'damo report damon --kernel_support'?
- Show intervals auto-tuning status on 'report access'
  - If the tuning is activated, show positive sample rate and current tuned intervals
- Update tuned intervals when getting snapshot, for only intervals auto-tuning
  enabled contexts
- Warn or error recording when intervals auto-tuning enabled.
  - Disabling auto-tuning is another option.
- damo report access: show '<access observation ratio>' by default if
  auto-tuning ongoing
- add DAMOS stat on 'damo report access' output by default if eligible
- Make 'damo report access' under auto-tuning smoother
  - It is not smooth since installing monitoring scheme updates
    sampling/aggregation intervals together.
  - Even if a monitoring scheme is installed, scheme target age comparison
    mismatches, since the comparison is done with age in aggregation unit that
    translated from max using the auto-tuned sampling interval.
    - Ideas
      - use min sampling interval?
      - treat larger than a value as same
  - Current workaround is using --tried_regions_of
  - Having to wait one aggregation interval for tried_regions update is too long.
    - DAMON sysfs may be able to be updated for this, for stat-only scheme.
- Support multiple kdamonds from command line interface
  (https://github.com/damonitor/damo/issues/3#issuecomment-2764663341)
- Support active page filter feature check

- Deprecate old features
  - Deprecate 'damo report raw'
  - Deprecate 'damo status' (done.)
  - Deprecate 'damo show' (done.)
  - Deprecate heats report type in favor of heatmap report type (done.)
  - Deprecate translate_damos (done.)
  - Deprecate single line per-scheme (done.  code moved to _damon_deprecated)
  - Deprecate v1-v3 schemes (done.  necessary code moved to _damon_deprecated)
  - Deprecate python2 support (done.  code moved to _damon_deprecated)
  - Deprecate scheme subcommand
    - Can be replaced by start or tune
  - Deprecate old scheme usages in tests
  - Deprecate DAMON results record binary format (done.  code moved to
    _damon_deprecated)
