From: "Vishal Moola (Oracle)" <vishal.moola@gmail.com>
To: Yueyang Pan <pyyjason@gmail.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Michal Hocko <mhocko@suse.com>,
Brendan Jackman <jackmanb@google.com>,
Johannes Weiner <hannes@cmpxchg.org>, Zi Yan <ziy@nvidia.com>,
Shakeel Butt <shakeel.butt@linux.dev>,
Usama Arif <usamaarif642@gmail.com>,
linux-mm@kvack.org, kernel-team@meta.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] mm/show_mem: Dump the status of the mem alloc profiling before printing
Date: Wed, 3 Sep 2025 12:07:25 -0700 [thread overview]
Message-ID: <aLiR7Rc24sUeun0i@fedora> (raw)
In-Reply-To: <d7998ea0ddc2ea1a78bb6e89adf530526f76679a.1756897825.git.pyyjason@gmail.com>
On Wed, Sep 03, 2025 at 04:16:13AM -0700, 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>
Reviewed-by: Vishal Moola (Oracle) <vishal.moola@gmail.com>
next prev parent reply other threads:[~2025-09-03 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 11:16 [PATCH v3 0/2] mm/show_mem: Bug fix for print mem alloc info Yueyang Pan
2025-09-03 11:16 ` [PATCH v3 1/2] mm/show_mem: Dump the status of the mem alloc profiling before printing Yueyang Pan
2025-09-03 15:49 ` Usama Arif
2025-09-03 16:10 ` Vlastimil Babka
2025-09-03 16:29 ` Zi Yan
2025-09-03 17:07 ` Suren Baghdasaryan
2025-09-03 19:07 ` Vishal Moola (Oracle) [this message]
2025-09-04 23:53 ` Shakeel Butt
2025-09-03 11:16 ` [PATCH v3 2/2] mm/show_mem: Add trylock while printing alloc info Yueyang Pan
2025-09-03 15:48 ` Usama Arif
2025-09-03 16:10 ` Vlastimil Babka
2025-09-03 16:30 ` Zi Yan
2025-09-03 17:08 ` Suren Baghdasaryan
2025-09-04 23:53 ` Shakeel Butt
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=aLiR7Rc24sUeun0i@fedora \
--to=vishal.moola@gmail.com \
--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=vbabka@suse.cz \
--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