All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
Cc: SJ Park <sj@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	damon@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [RFC PATCH v2 25/27] Docs/mm/damon/design: update for user report support
Date: Tue, 17 Nov 2026 18:22:20 -0800	[thread overview]
Message-ID: <20261118022225.100659-26-sj@kernel.org> (raw)
In-Reply-To: <20261118022225.100659-1-sj@kernel.org>

Update DAMON design document for the newly aded user_report type data
attribute reports.

Signed-off-by: SJ Park <sj@kernel.org>
---
 Documentation/mm/damon/design.rst | 15 ++++++++++++++-
 1 file changed, 14 insertions(+), 1 deletion(-)

diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
index 31ca623385718..39b508bc572c3 100644
--- a/Documentation/mm/damon/design.rst
+++ b/Documentation/mm/damon/design.rst
@@ -382,12 +382,25 @@ can generate and submit reports of the given type.  The generations and
 submissions could be done automatically by the kernel or manually by the user,
 depending on the type of the report.
 
-For now, no report type is supported.
+Below report types are supported.
+
+- ``user_report``: User-provided report.  To use this, the user should set the
+  address range of the memory to report for.  This type of report is not
+  automatically generated and submitted to DAMON.  The user should manually
+  generate and submit each report using the interface.
 
 The data attribute probe supports the reports.  The probes can be configured to
 hit for a given memory region if a specific type of valid reports that are
 associated with the probing memory exist in the reports queue.
 
+For example, users can run DAMON in the classical page table accessed bits
+based access monitoring.  In addition to that, users could find hot data that
+might not be able to found by DAMON.  DAMON might not able to find that due to
+limitations in page table accessed bits or its overhead control mechanism.
+Users may be able to find that using their access to workload source code,
+experiment results or other tools.  Users can complement monitoring results by
+feeding the information as user reports.
+
 Dynamic Target Space Updates Handling
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-- 
2.47.3

  parent reply	other threads:[~2026-11-18  2:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18  2:21 [RFC PATCH v2 00/27] mm/damon: let users report their data attribute findings SJ Park
2026-11-18  2:21 ` [RFC PATCH v2 01/27] mm/damon/api: introduce struct damon_report SJ Park
2026-11-18  2:21 ` [RFC PATCH v2 02/27] mm/damon/core: implement data attribute report queue SJ Park
2026-11-18  2:21 ` [RFC PATCH v2 03/27] mm/damon/core: introduce damon_submit_report() SJ Park
2026-11-18  2:21 ` [RFC PATCH v2 04/27] mm/damon/sysfs: add admin/reports/ directory SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 05/27] mm/damon/sysfs: add reports/producers/ directory SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 06/27] mm/damon/sysfs: add producers/nr_producers file SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 07/27] mm/damon/sysfs: implement report producer directory SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 08/27] mm/damon/sysfs: implement report producer type and state files SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 09/27] Docs/mm/damon/design: update for report system SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 10/27] Docs/admin-guide/mm/damon/usage: update for report producer sysfs SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 11/27] Docs/ABI/damon: update for report producer sysfs files SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 12/27] mm/damon/core: introduce DAMON_FILTER_TYPE_REPORT_MADE SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 13/27] mm/damon/core: introduce damon_report_exist() SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 14/27] mm/damon/paddr: support REPORT_MADE type probe filter SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 15/27] mm/damon/sysfs: add filter_report_type file under probe filter directory SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 16/27] mm/damon/sysfs: support REPORT_MADE type probe filter setup SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 17/27] Docs/mm/damon/design: update for report_made probe filter type SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 18/27] Docs/admin-guide/mm/damon/usage: update for REPORT_MADE probe filter SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 19/27] Docs/ABI/damon: " SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 20/27] mm/damon/api: introduce user_report report type SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 21/27] mm/damon/sysfs: add user_report support for report type input SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 22/27] mm/damon/sysfs: implement report producer addr_{start,end} files SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 23/27] mm/damon/sysfs: implement submit command for report producer SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 24/27] selftests/damon/sysfs.sh: add basic tests for admin/reports/ SJ Park
2026-11-18  2:22 ` SJ Park [this message]
2026-11-18  2:22 ` [RFC PATCH v2 26/27] Docs/admin-guide/mm/damon/usage: update for user_report report support SJ Park
2026-11-18  2:22 ` [RFC PATCH v2 27/27] Docs/ABI/damon: " SJ Park

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261118022225.100659-26-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.