From: Stefan Roesch <shr@devkernel.io>
To: kernel-team@fb.com
Cc: shr@devkernel.io, akpm@linux-foundation.org, david@redhat.com,
hannes@cmpxchg.org, riel@surriel.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH v1 3/4] mm/ksm: add tracepoint for ksm advisor
Date: Wed, 4 Oct 2023 12:02:48 -0700 [thread overview]
Message-ID: <20231004190249.829015-4-shr@devkernel.io> (raw)
In-Reply-To: <20231004190249.829015-1-shr@devkernel.io>
This adds a new tracepoint for the ksm advisor. It reports the last scan
time and the new setting of the pages_to_scan parameter.
Signed-off-by: Stefan Roesch <shr@devkernel.io>
---
include/trace/events/ksm.h | 28 ++++++++++++++++++++++++++++
mm/ksm.c | 2 ++
2 files changed, 30 insertions(+)
diff --git a/include/trace/events/ksm.h b/include/trace/events/ksm.h
index b5ac35c1d0e8..164133014922 100644
--- a/include/trace/events/ksm.h
+++ b/include/trace/events/ksm.h
@@ -245,6 +245,34 @@ TRACE_EVENT(ksm_remove_rmap_item,
__entry->pfn, __entry->rmap_item, __entry->mm)
);
+/**
+ * ksm_advisor - called after the advisor has run
+ *
+ * @scan_time: scan time in seconds
+ * @pages_to_scan: new pages_to_scan value
+ *
+ * Allows to trace the ksm advisor.
+ */
+TRACE_EVENT(ksm_advisor,
+
+ TP_PROTO(s64 scan_time, unsigned long pages_to_scan),
+
+ TP_ARGS(scan_time, pages_to_scan),
+
+ TP_STRUCT__entry(
+ __field(s64, scan_time)
+ __field(unsigned long, pages_to_scan)
+ ),
+
+ TP_fast_assign(
+ __entry->scan_time = scan_time;
+ __entry->pages_to_scan = pages_to_scan;
+ ),
+
+ TP_printk("ksm scan time %lld pages_to_scan %lu",
+ __entry->scan_time, __entry->pages_to_scan)
+);
+
#endif /* _TRACE_KSM_H */
/* This part must be outside protection */
diff --git a/mm/ksm.c b/mm/ksm.c
index 12e70f806b2b..93dff974f6ea 100644
--- a/mm/ksm.c
+++ b/mm/ksm.c
@@ -415,6 +415,8 @@ static void scan_time_advisor(s64 scan_time)
advisor_ctx.change = change;
advisor_ctx.scan_time = scan_time;
ksm_thread_pages_to_scan = pages;
+
+ trace_ksm_advisor(scan_time, pages);
}
static void run_advisor(void)
--
2.39.3
next prev parent reply other threads:[~2023-10-04 19:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 19:02 [PATCH v1 0/4] mm/ksm: Add " Stefan Roesch
2023-10-04 19:02 ` [PATCH v1 1/4] mm/ksm: add " Stefan Roesch
2023-10-04 19:02 ` [PATCH v1 2/4] mm/ksm: add sysfs knobs for advisor Stefan Roesch
2023-10-05 17:57 ` kernel test robot
2023-10-05 21:36 ` kernel test robot
2023-10-04 19:02 ` Stefan Roesch [this message]
2023-10-04 19:02 ` [PATCH v1 4/4] mm/ksm: document ksm advisor and its sysfs knobs Stefan Roesch
2023-10-06 12:01 ` [PATCH v1 0/4] mm/ksm: Add ksm advisor David Hildenbrand
2023-10-06 16:17 ` Stefan Roesch
2023-10-09 9:48 ` David Hildenbrand
2023-10-10 16:02 ` Stefan Roesch
2023-10-17 15:28 ` David Hildenbrand
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=20231004190249.829015-4-shr@devkernel.io \
--to=shr@devkernel.io \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox