From: "Uladzislau Rezki (Sony)" <urezki@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Matthew Wilcox <willy@infradead.org>,
Nicholas Piggin <npiggin@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Uladzislau Rezki <urezki@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: [PATCH v2 2/7] mm: vmalloc: Add purge_vmap_area_lazy trace event
Date: Tue, 18 Oct 2022 20:10:48 +0200 [thread overview]
Message-ID: <20221018181053.434508-3-urezki@gmail.com> (raw)
In-Reply-To: <20221018181053.434508-1-urezki@gmail.com>
It is for debug purpose to track number of freed vmap
areas including a range it occurs on.
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
include/trace/events/vmalloc.h | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/include/trace/events/vmalloc.h b/include/trace/events/vmalloc.h
index 39fbd77c91e7..afeb8003a0f2 100644
--- a/include/trace/events/vmalloc.h
+++ b/include/trace/events/vmalloc.h
@@ -50,6 +50,39 @@ TRACE_EVENT(alloc_vmap_area,
__entry->vstart, __entry->vend, __entry->failed)
);
+/**
+ * purge_vmap_area_lazy - called when vmap areas were lazily freed
+ * @start: purging start address
+ * @end: purging end address
+ * @npurged: numbed of purged vmap areas
+ *
+ * This event is used for a debug purpose. It gives some
+ * indication about start:end range and how many objects
+ * are released.
+ */
+TRACE_EVENT(purge_vmap_area_lazy,
+
+ TP_PROTO(unsigned long start, unsigned long end,
+ unsigned int npurged),
+
+ TP_ARGS(start, end, npurged),
+
+ TP_STRUCT__entry(
+ __field(unsigned long, start)
+ __field(unsigned long, end)
+ __field(unsigned int, npurged)
+ ),
+
+ TP_fast_assign(
+ __entry->start = start;
+ __entry->end = end;
+ __entry->npurged = npurged;
+ ),
+
+ TP_printk("start=0x%lx end=0x%lx num_purged=%u",
+ __entry->start, __entry->end, __entry->npurged)
+);
+
#endif /* _TRACE_VMALLOC_H */
/* This part must be outside protection */
--
2.30.2
next prev parent reply other threads:[~2022-10-18 18:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 18:10 [PATCH v2 0/7] Add basic trace events for vmap/vmalloc (v2) Uladzislau Rezki (Sony)
2022-10-18 18:10 ` [PATCH v2 1/7] mm: vmalloc: Add alloc_vmap_area trace event Uladzislau Rezki (Sony)
2022-10-20 11:22 ` Christoph Hellwig
2022-11-14 15:53 ` Steven Rostedt
2022-11-14 16:55 ` Uladzislau Rezki
2022-10-18 18:10 ` Uladzislau Rezki (Sony) [this message]
2022-10-20 11:22 ` [PATCH v2 2/7] mm: vmalloc: Add purge_vmap_area_lazy " Christoph Hellwig
2022-10-18 18:10 ` [PATCH v2 4/7] mm: vmalloc: Use trace_alloc_vmap_area event Uladzislau Rezki (Sony)
2022-10-20 11:23 ` Christoph Hellwig
2022-10-18 18:10 ` [PATCH v2 5/7] mm: vmalloc: Use trace_purge_vmap_area_lazy event Uladzislau Rezki (Sony)
2022-10-20 11:25 ` Christoph Hellwig
2022-10-20 12:55 ` Uladzislau Rezki
2022-10-23 22:51 ` kernel test robot
2022-10-24 12:48 ` Uladzislau Rezki
2022-10-18 18:10 ` [PATCH v2 6/7] mm: vmalloc: Use trace_free_vmap_area_noflush event Uladzislau Rezki (Sony)
2022-10-20 11:25 ` Christoph Hellwig
2022-10-18 18:10 ` [PATCH v2 7/7] vmalloc: Add reviewers for vmalloc code Uladzislau Rezki (Sony)
2022-10-20 11:25 ` Christoph Hellwig
2022-10-18 18:23 ` [PATCH v2 0/7] Add basic trace events for vmap/vmalloc (v2) Steven Rostedt
2022-10-18 18:25 ` Steven Rostedt
2022-10-19 11:49 ` Uladzislau Rezki
[not found] ` <20221018181053.434508-4-urezki@gmail.com>
2022-10-20 11:22 ` [PATCH v2 3/7] mm: vmalloc: Add free_vmap_area_noflush trace event Christoph Hellwig
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=20221018181053.434508-3-urezki@gmail.com \
--to=urezki@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@gmail.com \
--cc=oleksiy.avramchenko@sony.com \
--cc=rostedt@goodmis.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox