162306a36Sopenharmony_ci.. SPDX-License-Identifier: GPL-2.0 262306a36Sopenharmony_ci 362306a36Sopenharmony_ciDAMON Maintainer Entry Profile 462306a36Sopenharmony_ci============================== 562306a36Sopenharmony_ci 662306a36Sopenharmony_ciThe DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR' 762306a36Sopenharmony_cisection of 'MAINTAINERS' file. 862306a36Sopenharmony_ci 962306a36Sopenharmony_ciThe mailing lists for the subsystem are damon@lists.linux.dev and 1062306a36Sopenharmony_cilinux-mm@kvack.org. Patches should be made against the mm-unstable tree [1]_ 1162306a36Sopenharmony_ciwhenever possible and posted to the mailing lists. 1262306a36Sopenharmony_ci 1362306a36Sopenharmony_ciSCM Trees 1462306a36Sopenharmony_ci--------- 1562306a36Sopenharmony_ci 1662306a36Sopenharmony_ciThere are multiple Linux trees for DAMON development. Patches under 1762306a36Sopenharmony_cidevelopment or testing are queued in damon/next [2]_ by the DAMON maintainer. 1862306a36Sopenharmony_ciSufficiently reviewed patches will be queued in mm-unstable [1]_ by the memory 1962306a36Sopenharmony_cimanagement subsystem maintainer. After more sufficient tests, the patches will 2062306a36Sopenharmony_cibe queued in mm-stable [3]_ , and finally pull-requested to the mainline by the 2162306a36Sopenharmony_cimemory management subsystem maintainer. 2262306a36Sopenharmony_ci 2362306a36Sopenharmony_ciNote again the patches for review should be made against the mm-unstable 2462306a36Sopenharmony_citree[1] whenever possible. damon/next is only for preview of others' works in 2562306a36Sopenharmony_ciprogress. 2662306a36Sopenharmony_ci 2762306a36Sopenharmony_ciSubmit checklist addendum 2862306a36Sopenharmony_ci------------------------- 2962306a36Sopenharmony_ci 3062306a36Sopenharmony_ciWhen making DAMON changes, you should do below. 3162306a36Sopenharmony_ci 3262306a36Sopenharmony_ci- Build changes related outputs including kernel and documents. 3362306a36Sopenharmony_ci- Ensure the builds introduce no new errors or warnings. 3462306a36Sopenharmony_ci- Run and ensure no new failures for DAMON selftests [4]_ and kunittests [5]_ . 3562306a36Sopenharmony_ci 3662306a36Sopenharmony_ciFurther doing below and putting the results will be helpful. 3762306a36Sopenharmony_ci 3862306a36Sopenharmony_ci- Run damon-tests/corr [6]_ for normal changes. 3962306a36Sopenharmony_ci- Run damon-tests/perf [7]_ for performance changes. 4062306a36Sopenharmony_ci 4162306a36Sopenharmony_ciKey cycle dates 4262306a36Sopenharmony_ci--------------- 4362306a36Sopenharmony_ci 4462306a36Sopenharmony_ciPatches can be sent anytime. Key cycle dates of the mm-unstable[1] and 4562306a36Sopenharmony_cimm-stable[3] trees depend on the memory management subsystem maintainer. 4662306a36Sopenharmony_ci 4762306a36Sopenharmony_ciReview cadence 4862306a36Sopenharmony_ci-------------- 4962306a36Sopenharmony_ci 5062306a36Sopenharmony_ciThe DAMON maintainer does the work on the usual work hour (09:00 to 17:00, 5162306a36Sopenharmony_ciMon-Fri) in PST. The response to patches will occasionally be slow. Do not 5262306a36Sopenharmony_cihesitate to send a ping if you have not heard back within a week of sending a 5362306a36Sopenharmony_cipatch. 5462306a36Sopenharmony_ci 5562306a36Sopenharmony_ci 5662306a36Sopenharmony_ci.. [1] https://git.kernel.org/akpm/mm/h/mm-unstable 5762306a36Sopenharmony_ci.. [2] https://git.kernel.org/sj/h/damon/next 5862306a36Sopenharmony_ci.. [3] https://git.kernel.org/akpm/mm/h/mm-stable 5962306a36Sopenharmony_ci.. [4] https://github.com/awslabs/damon-tests/blob/master/corr/run.sh#L49 6062306a36Sopenharmony_ci.. [5] https://github.com/awslabs/damon-tests/blob/master/corr/tests/kunit.sh 6162306a36Sopenharmony_ci.. [6] https://github.com/awslabs/damon-tests/tree/master/corr 6262306a36Sopenharmony_ci.. [7] https://github.com/awslabs/damon-tests/tree/master/perf 63