From: SeongJae Park Date: Wed, 21 May 2025 04:27:55 +0000 (-0700) Subject: mm/damon/Kconfig: enable CONFIG_DAMON by default X-Git-Tag: v6.16-rc1~73^2~19 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=28615e6eed152f2fda5486680090b74aeed7b554;p=thirdparty%2Fkernel%2Flinux.git mm/damon/Kconfig: enable CONFIG_DAMON by default As of this writing, multiple major distros including Alma, Amazon, Android, CentOS, Debian, Fedora, and Oracle are build-enabling DAMON (set CONFIG_DAMON[1]). Enabling it by default will save configuration setup time for the current and future DAMON users. Build-enabling DAMON does not introduce a real risk since it makes no behavioral change by default. It requires explicit user requests to do anything. Only one potential risk is making the size of the kernel a little bit larger. On a production-purpose configuration, it increases the resulting kernel package size by about 0.1 % of the final package file. I believe that's too small to be a real problem in common setups. Hence, the benefit of enabling CONFIG_DAMON outweighs the potential risk. Set CONFIG_DAMON by default. Link: https://oracle.github.io/kconfigs/?config=UTS_RELEASE&config=DAMON [1] Link: https://lkml.kernel.org/r/20250521042755.39653-3-sj@kernel.org Signed-off-by: SeongJae Park Acked-by: Honggyu Kim Signed-off-by: Andrew Morton --- diff --git a/mm/damon/Kconfig b/mm/damon/Kconfig index c93d0c56b9639..551745df011b7 100644 --- a/mm/damon/Kconfig +++ b/mm/damon/Kconfig @@ -4,6 +4,7 @@ menu "Data Access Monitoring" config DAMON bool "DAMON: Data Access Monitoring Framework" + default y help This builds a framework that allows kernel subsystems to monitor access frequency of each memory region. The information can be useful