From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,surenb@google.com,kent.overstreet@linux.dev,gehao@kylinos.cn,akpm@linux-foundation.org
Subject: [to-be-updated] mm-alloc_tag-add-the-arch_needs_weak_per_cpu-macro-when-statically-defining-the-percpu-variable-alloc_tag_counters.patch removed from -mm tree
Date: Mon, 09 Jun 2025 17:04:16 -0700 [thread overview]
Message-ID: <20250610000417.31BF9C4CEEB@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/alloc_tag: add the ARCH_NEEDS_WEAK_PER_CPU macro when statically defining the percpu variable alloc_tag_counters
has been removed from the -mm tree. Its filename was
mm-alloc_tag-add-the-arch_needs_weak_per_cpu-macro-when-statically-defining-the-percpu-variable-alloc_tag_counters.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: Hao Ge <gehao@kylinos.cn>
Subject: mm/alloc_tag: add the ARCH_NEEDS_WEAK_PER_CPU macro when statically defining the percpu variable alloc_tag_counters
Date: Thu, 29 May 2025 15:35:37 +0800
Recently discovered this entry while checking kallsyms on ARM64:
ffff800083e509c0 D _shared_alloc_tag
If ARCH_NEEDS_WEAK_PER_CPU is not defined,there's no need to statically
define the percpu variable alloc_tag_counters.
Therefore, add the relevant macro guards at the appropriate location.
Link: https://lkml.kernel.org/r/20250529073537.563107-1-hao.ge@linux.dev
Fixes: 22d407b164ff ("lib: add allocation tagging support for memory allocation profiling")
Signed-off-by: Hao Ge <gehao@kylinos.cn>
Cc: Kent Overstreet <kent.overstreet@linux.dev>
Cc: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/alloc_tag.c | 2 ++
1 file changed, 2 insertions(+)
--- a/lib/alloc_tag.c~mm-alloc_tag-add-the-arch_needs_weak_per_cpu-macro-when-statically-defining-the-percpu-variable-alloc_tag_counters
+++ a/lib/alloc_tag.c
@@ -24,8 +24,10 @@ static bool mem_profiling_support;
static struct codetag_type *alloc_tag_cttype;
+#ifdef ARCH_NEEDS_WEAK_PER_CPU
DEFINE_PER_CPU(struct alloc_tag_counters, _shared_alloc_tag);
EXPORT_SYMBOL(_shared_alloc_tag);
+#endif /* ARCH_NEEDS_WEAK_PER_CPU */
DEFINE_STATIC_KEY_MAYBE(CONFIG_MEM_ALLOC_PROFILING_ENABLED_BY_DEFAULT,
mem_alloc_profiling_key);
_
Patches currently in -mm which might be from gehao@kylinos.cn are
reply other threads:[~2025-06-10 0:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250610000417.31BF9C4CEEB@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=gehao@kylinos.cn \
--cc=kent.overstreet@linux.dev \
--cc=mm-commits@vger.kernel.org \
--cc=surenb@google.com \
/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.