From: Vlastimil Babka <vbabka@suse.cz>
To: Yueyang Pan <pyyjason@gmail.com>,
Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Vishal Moola <vishal.moola@gmail.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Usama Arif <usamaarif642@gmail.com>
Cc: linux-mm@kvack.org, kernel-team@meta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] mm/show_mem: Dump the status of the mem alloc profiling before printing
Date: Wed, 3 Sep 2025 11:26:01 +0200 [thread overview]
Message-ID: <ef1b79ab-15cb-4720-ab05-d77617143a26@suse.cz> (raw)
In-Reply-To: <8dc71d31de53afa4c0bb25234807b1e6ead5ba55.1756827906.git.pyyjason@gmail.com>
On 9/2/25 17:57, Yueyang Pan wrote:
> This patch prints the status of the memory allocation profiling
> before __show_mem actually prints the detailed allocation info.
> This way will let us know the `0B` we saw in allocation info is
> because the profiling is disabled or the allocation is actually
> 0B.
>
> Signed-off-by: Yueyang Pan <pyyjason@gmail.com>
> ---
> mm/show_mem.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/show_mem.c b/mm/show_mem.c
> index ecf20a93ea54..51892ce2efc4 100644
> --- a/mm/show_mem.c
> +++ b/mm/show_mem.c
> @@ -427,6 +427,8 @@ void __show_mem(unsigned int filter, nodemask_t *nodemask, int max_zone_idx)
>
> nr = alloc_tag_top_users(tags, ARRAY_SIZE(tags), false);
> if (nr) {
> + pr_notice("Memory alloction profiling is turned %s\n",
There's a typo "alloction".
> + mem_alloc_profiling_enabled() ? "on" : "off");
> pr_notice("Memory allocations:\n");
But I think the message would be more obvious if it said e.g.:
"Memory allocations (profiling is currently [on/off]):"
> for (i = 0; i < nr; i++) {
> struct codetag *ct = tags[i].ct;
next prev parent reply other threads:[~2025-09-03 9:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 15:57 [PATCH v2 0/2] mm/show_mem: Bug fix for print mem alloc info Yueyang Pan
2025-09-02 15:57 ` [PATCH v2 1/2] mm/show_mem: Dump the status of the mem alloc profiling before printing Yueyang Pan
2025-09-03 9:26 ` Vlastimil Babka [this message]
2025-09-03 9:34 ` Yueyang Pan
2025-09-03 10:12 ` Vlastimil Babka
2025-09-03 10:12 ` Usama Arif
2025-09-02 15:57 ` [PATCH v2 2/2] mm/show_mem: Add trylock while printing alloc info Yueyang Pan
2025-09-03 9:22 ` Vlastimil Babka
2025-09-03 9:31 ` Usama Arif
2025-09-03 9:47 ` kernel test robot
2025-09-03 10:16 ` Vlastimil Babka
2025-09-03 10:24 ` Yueyang Pan
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=ef1b79ab-15cb-4720-ab05-d77617143a26@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pyyjason@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=usamaarif642@gmail.com \
--cc=vishal.moola@gmail.com \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox