maintainer-profile.rst 4.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105
  1. .. SPDX-License-Identifier: GPL-2.0
  2. DAMON Maintainer Entry Profile
  3. ==============================
  4. The DAMON subsystem covers the files that are listed in 'DATA ACCESS MONITOR'
  5. section of 'MAINTAINERS' file.
  6. The mailing lists for the subsystem are damon@lists.linux.dev and
  7. linux-mm@kvack.org. Patches should be made against the `mm-unstable tree
  8. <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ whenever possible and posted
  9. to the mailing lists.
  10. SCM Trees
  11. ---------
  12. There are multiple Linux trees for DAMON development. Patches under
  13. development or testing are queued in `damon/next
  14. <https://git.kernel.org/sj/h/damon/next>`_ by the DAMON maintainer.
  15. Sufficiently reviewed patches will be queued in `mm-unstable
  16. <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ by the memory management
  17. subsystem maintainer. After more sufficient tests, the patches will be queued
  18. in `mm-stable <https://git.kernel.org/akpm/mm/h/mm-stable>`_, and finally
  19. pull-requested to the mainline by the memory management subsystem maintainer.
  20. Note again the patches for `mm-unstable tree
  21. <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ are queued by the memory
  22. management subsystem maintainer. If the patches requires some patches in
  23. `damon/next tree <https://git.kernel.org/sj/h/damon/next>`_ which not yet merged
  24. in mm-unstable, please make sure the requirement is clearly specified.
  25. Submit checklist addendum
  26. -------------------------
  27. When making DAMON changes, you should do below.
  28. - Build changes related outputs including kernel and documents.
  29. - Ensure the builds introduce no new errors or warnings.
  30. - Run and ensure no new failures for DAMON `selftests
  31. <https://github.com/damonitor/damon-tests/blob/master/corr/run.sh#L49>`_ and
  32. `kunittests
  33. <https://github.com/damonitor/damon-tests/blob/master/corr/tests/kunit.sh>`_.
  34. Further doing below and putting the results will be helpful.
  35. - Run `damon-tests/corr
  36. <https://github.com/damonitor/damon-tests/tree/master/corr>`_ for normal
  37. changes.
  38. - Run `damon-tests/perf
  39. <https://github.com/damonitor/damon-tests/tree/master/perf>`_ for performance
  40. changes.
  41. Key cycle dates
  42. ---------------
  43. Patches can be sent anytime. Key cycle dates of the `mm-unstable
  44. <https://git.kernel.org/akpm/mm/h/mm-unstable>`_ and `mm-stable
  45. <https://git.kernel.org/akpm/mm/h/mm-stable>`_ trees depend on the memory
  46. management subsystem maintainer.
  47. Review cadence
  48. --------------
  49. The DAMON maintainer does the work on the usual work hour (09:00 to 17:00,
  50. Mon-Fri) in PT (Pacific Time). The response to patches will occasionally be
  51. slow. Do not hesitate to send a ping if you have not heard back within a week
  52. of sending a patch.
  53. Mailing tool
  54. ------------
  55. Like many other Linux kernel subsystems, DAMON uses the mailing lists
  56. (damon@lists.linux.dev and linux-mm@kvack.org) as the major communication
  57. channel. There is a simple tool called `HacKerMaiL
  58. <https://github.com/damonitor/hackermail>`_ (``hkml``), which is for people who
  59. are not very familiar with the mailing lists based communication. The tool
  60. could be particularly helpful for DAMON community members since it is developed
  61. and maintained by DAMON maintainer. The tool is also officially announced to
  62. support DAMON and general Linux kernel development workflow.
  63. In other words, `hkml <https://github.com/damonitor/hackermail>`_ is a mailing
  64. tool for DAMON community, which DAMON maintainer is committed to support.
  65. Please feel free to try and report issues or feature requests for the tool to
  66. the maintainer.
  67. Community meetup
  68. ----------------
  69. DAMON community is maintaining two bi-weekly meetup series for community
  70. members who prefer synchronous conversations over mails.
  71. The first one is for any discussion between every community member. No
  72. reservation is needed.
  73. The seconds one is for discussions on specific topics between restricted
  74. members including the maintainer. The maintainer shares the available time
  75. slots, and attendees should reserve one of those at least 24 hours before the
  76. time slot, by reaching out to the maintainer.
  77. Schedules and available reservation time slots are available at the Google `doc
  78. <https://docs.google.com/document/d/1v43Kcj3ly4CYqmAkMaZzLiM2GEnWfgdGbZAH3mi2vpM/edit?usp=sharing>`_.
  79. There is also a public Google `calendar
  80. <https://calendar.google.com/calendar/u/0?cid=ZDIwOTA4YTMxNjc2MDQ3NTIyMmUzYTM5ZmQyM2U4NDA0ZGIwZjBiYmJlZGQxNDM0MmY4ZTRjOTE0NjdhZDRiY0Bncm91cC5jYWxlbmRhci5nb29nbGUuY29t>`_
  81. that has the events. Anyone can subscribe it. DAMON maintainer will also
  82. provide periodic reminder to the mailing list (damon@lists.linux.dev).