All of lore.kernel.org
 help / color / mirror / Atom feed
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 3/7] mm: vmap: Add a free_vmap_area_noflush trace event
Date: Mon, 17 Oct 2022 18:02:28 +0200	[thread overview]
Message-ID: <20221017160233.16582-5-urezki@gmail.com> (raw)
In-Reply-To: <20221017160233.16582-1-urezki@gmail.com>

This event is used in order to validate/debug a start address
of freed VA, number of currently outstanding and maximum allowed
areas.

To: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
 include/trace/events/vmap.h | 34 ++++++++++++++++++++++++++++++++++
 1 file changed, 34 insertions(+)

diff --git a/include/trace/events/vmap.h b/include/trace/events/vmap.h
index 2af2b84c6eb7..5ba9bf58772a 100644
--- a/include/trace/events/vmap.h
+++ b/include/trace/events/vmap.h
@@ -83,6 +83,40 @@ TRACE_EVENT(purge_vmap_area_lazy,
 		__entry->start, __entry->end, __entry->npurged)
 );
 
+/**
+ * free_vmap_area_noflush - called when a vmap area is freed
+ * @va_start:		a start address of VA
+ * @nr_lazy:		number of current lazy pages
+ * @nr_lazy_max:	number of maximum lazy pages
+ *
+ * This event is used for a debug purpose. It gives some
+ * indication about a VA that is released, number of current
+ * outstanding areas and a maximum allowed threshold before
+ * dropping all of them.
+ */
+TRACE_EVENT(free_vmap_area_noflush,
+
+	TP_PROTO(unsigned long va_start, unsigned long nr_lazy,
+		unsigned long nr_lazy_max),
+
+	TP_ARGS(va_start, nr_lazy, nr_lazy_max),
+
+	TP_STRUCT__entry(
+		__field(unsigned long, va_start)
+		__field(unsigned long, nr_lazy)
+		__field(unsigned long, nr_lazy_max)
+	),
+
+	TP_fast_assign(
+		__entry->va_start = va_start;
+		__entry->nr_lazy = nr_lazy;
+		__entry->nr_lazy_max = nr_lazy_max;
+	),
+
+	TP_printk("va_start=0x%lx nr_lazy=%lu nr_lazy_max=%lu",
+		__entry->va_start, __entry->nr_lazy, __entry->nr_lazy_max)
+);
+
 #endif /*  _TRACE_VMAP_H */
 
 /* This part must be outside protection */
-- 
2.30.2



  parent reply	other threads:[~2022-10-17 16:02 UTC|newest]

Thread overview: 19+ 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 ` [PATCH 2/7] mm: vmap: Add " Uladzislau Rezki (Sony)
2022-10-17 16:02 ` Uladzislau Rezki (Sony) [this message]
2022-10-17 16:02 ` [PATCH 3/7] mm: vmap: Add free_vmap_area_noflush " 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:17       ` Uladzislau Rezki
2022-10-18 16:44       ` Steven Rostedt
2022-10-18 16:44         ` Steven Rostedt
2022-10-18 16:55         ` Uladzislau Rezki
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-5-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 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.