From: Andrew Morton <akpm@linux-foundation.org>
To: 高翔 <gaoxiang17@xiaomi.com>
Cc: Xiang Gao <gxxa03070307@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 答复: [External Mail]Re: [PATCH] mm/cma.c: To better understand cma area during debugging, add total and used count logs to in cma_alloc
Date: Wed, 25 Sep 2024 06:15:36 -0700 [thread overview]
Message-ID: <20240925061536.e8abdbac3217d85f6f99afd5@linux-foundation.org> (raw)
In-Reply-To: <fc8822dd647c4aafbb72a83f5f57c6f1@xiaomi.com>
On Wed, 25 Sep 2024 12:00:56 +0000 高翔 <gaoxiang17@xiaomi.com> wrote:
> > [ 24.225125] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 64, request count 1, align 0)
> > [ 24.231963] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 65, request count 1, align 0)
> > [ 24.235712] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 66, request count 1, align 0)
> >
>
>
> Above is the cma alloc during boot. The before-and-after context has nothing to do with cma alloc. Below is the log with before-and-after context added.
>
>
> [ 24.006605] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
> [ 24.071644] Serial: AMBA driver
> [ 24.096063] arm-smmu-v3 9050000.smmuv3: ias 44-bit, oas 44-bit (features 0x00000305)
> [ 24.097989] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 64, request count 1, align 0)
> [ 24.104260] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 65, request count 1, align 0)
> [ 24.107504] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 66, request count 1, align 0)
> [ 24.140495] cacheinfo: Unable to detect cache hierarchy for CPU 0
> [ 24.484998] loop: module loaded
> [ 24.536152] virtio_blk virtio0: [vda] 4194304 512-byte logical blocks (2.15 GB/2.00 GiB)
What I mean is to paste the messages before the patch and to paste the
messages after the patch. So readers can easily see what changed.
next prev parent reply other threads:[~2024-09-25 13:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 12:43 Xiang Gao
2024-09-25 0:27 ` Andrew Morton
2024-09-25 12:00 ` 答复: [External Mail]Re: " 高翔
2024-09-25 13:15 ` Andrew Morton [this message]
2024-09-26 2:57 ` 答复: " 高翔
2024-09-25 13:02 ` 高翔
2024-09-26 10:52 ` David Hildenbrand
2024-09-26 11:51 ` 答复: [External Mail]Re: " 高翔
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=20240925061536.e8abdbac3217d85f6f99afd5@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gaoxiang17@xiaomi.com \
--cc=gxxa03070307@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox