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>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event
Date: Mon, 17 Oct 2022 18:02:30 +0200	[thread overview]
Message-ID: <20221017160233.16582-7-urezki@gmail.com> (raw)
In-Reply-To: <20221017160233.16582-1-urezki@gmail.com>

This is for debug purpose and is called when an allocation
attempt occurs. This event gives some information about:
- a start address of allocated area;
- a size that is requested;
- an align that is required;
- vstart/vend restriction;
- if an allocation fails.

Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Uladzislau Rezki (Sony) <urezki@gmail.com>
---
 mm/vmalloc.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/mm/vmalloc.c b/mm/vmalloc.c
index 83b54beb12fa..f4397817ccd7 100644
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -43,6 +43,9 @@
 #include <asm/tlbflush.h>
 #include <asm/shmparam.h>
 
+#define CREATE_TRACE_POINTS
+#include <trace/events/vmap.h>
+
 #include "internal.h"
 #include "pgalloc-track.h"
 
@@ -1621,6 +1624,8 @@ static struct vmap_area *alloc_vmap_area(unsigned long size,
 		size, align, vstart, vend);
 	spin_unlock(&free_vmap_area_lock);
 
+	trace_alloc_vmap_area(addr, size, align, vstart, vend, addr == vend);
+
 	/*
 	 * If an allocation fails, the "vend" address is
 	 * returned. Therefore trigger the overflow path.
-- 
2.30.2


  parent reply	other threads:[~2022-10-17 16:03 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 ` [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 ` Uladzislau Rezki (Sony) [this message]
2022-10-17 19:12   ` [PATCH 4/7] mm/vmalloc: Use a trace_alloc_vmap_area event 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-7-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 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.