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>,
Uladzislau Rezki <urezki@gmail.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>
Subject: [PATCH 2/7] mm: vmap: Add purge_vmap_area_lazy trace event
Date: Mon, 17 Oct 2022 18:02:27 +0200 [thread overview]
Message-ID: <20221017160233.16582-4-urezki@gmail.com> (raw)
In-Reply-To: <20221017160233.16582-1-urezki@gmail.com>
It is for debug purpose to track number of freed vmaps
including a range it occurs on.
To: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
include/trace/events/vmap.h | 33 +++++++++++++++++++++++++++++++++
1 file changed, 33 insertions(+)
diff --git a/include/trace/events/vmap.h b/include/trace/events/vmap.h
index 504870d95a4e..2af2b84c6eb7 100644
--- a/include/trace/events/vmap.h
+++ b/include/trace/events/vmap.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_VMAP_H */
/* This part must be outside protection */
--
2.30.2
next prev parent reply other threads:[~2022-10-17 16:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 16:02 [PATCH 0/7] Add basic trace events for vmap/vmalloc Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 1/7] mm: vmap: Add alloc_vmap_area trace event Uladzislau Rezki (Sony)
2022-10-18 16:41 ` Steven Rostedt
2022-10-18 16:57 ` Uladzislau Rezki
2022-10-17 16:02 ` [PATCH 2/7] mm: vmap: Add a purge_vmap_area_lazy " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` Uladzislau Rezki (Sony) [this message]
2022-10-17 16:02 ` [PATCH 3/7] mm: vmap: Add a free_vmap_area_noflush " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 3/7] mm: vmap: Add " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event Uladzislau Rezki (Sony)
2022-10-17 19:12 ` kernel test robot
2022-10-18 16:17 ` Uladzislau Rezki
2022-10-18 16:44 ` Steven Rostedt
2022-10-18 16:55 ` Uladzislau Rezki
2022-10-17 16:02 ` [PATCH 5/7] mm/vmalloc: Use a trace_purge_vmap_area_lazy event Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 6/7] mm/vmalloc: Use a trace_free_vmap_area_noflush event Uladzislau Rezki (Sony)
2022-10-17 16:02 ` [PATCH 7/7] vmalloc: Add reviewers for vmalloc code Uladzislau Rezki (Sony)
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=20221017160233.16582-4-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=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;
as well as URLs for NNTP newsgroup(s).