From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: kent.overstreet@linux.dev, hch@infradead.org, vbabka@suse.cz,
pasha.tatashin@soleen.com, souravpanda@google.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, surenb@google.com,
kernel test robot <lkp@intel.com>
Subject: [PATCH v2 1/2] alloc_tag: export mem_alloc_profiling_key used by modules
Date: Wed, 17 Jul 2024 11:12:38 -0700 [thread overview]
Message-ID: <20240717181239.2510054-1-surenb@google.com> (raw)
Export mem_alloc_profiling_key as it is used by modules (indirectly via
mem_alloc_profiling_enabled()).
Fixes: 22d407b164ff ("lib: add allocation tagging support for memory allocation profiling")
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202407080044.DWMC9N9I-lkp@intel.com/
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
---
Changes since v1 [1]
- Added Acked-by, per Vlastimil Babka
[1] https://lore.kernel.org/all/20240717011631.2150066-1-surenb@google.com/
lib/alloc_tag.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/alloc_tag.c b/lib/alloc_tag.c
index 81e5f9a70f22..832f79a32b3e 100644
--- a/lib/alloc_tag.c
+++ b/lib/alloc_tag.c
@@ -15,6 +15,7 @@ EXPORT_SYMBOL(_shared_alloc_tag);
DEFINE_STATIC_KEY_MAYBE(CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT,
mem_alloc_profiling_key);
+EXPORT_SYMBOL(mem_alloc_profiling_key);
struct allocinfo_private {
struct codetag_iterator iter;
base-commit: 51835949dda3783d4639cfa74ce13a3c9829de00
--
2.45.2.993.g49e7a77208-goog
next reply other threads:[~2024-07-17 18:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 18:12 Suren Baghdasaryan [this message]
2024-07-17 18:12 ` [PATCH v2 2/2] alloc_tag: outline and export free_reserved_page() Suren Baghdasaryan
2024-07-17 19:35 ` Vlastimil Babka
2024-07-17 20:04 ` Suren Baghdasaryan
2024-07-17 20:19 ` Vlastimil Babka
2024-07-17 21:20 ` Suren Baghdasaryan
2024-07-17 21:30 ` Suren Baghdasaryan
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=20240717181239.2510054-1-surenb@google.com \
--to=surenb@google.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=keescook@chromium.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=souravpanda@google.com \
--cc=vbabka@suse.cz \
/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