From: Rob Herring <robh@kernel.org>
To: Martin Liu <liumartin@google.com>
Cc: frowand.list@gmail.com, devicetree@vger.kernel.org,
minchan@kernel.org, tkjos@google.com,
linux-kernel@vger.kernel.org, surenb@google.com,
robh+dt@kernel.org
Subject: Re: [PATCH v2] of: reserved-mem: print out reserved-mem details during boot
Date: Wed, 15 Feb 2023 12:19:38 -0600 [thread overview]
Message-ID: <167648517621.362040.7176595866897785827.robh@kernel.org> (raw)
In-Reply-To: <20230209160954.1471909-1-liumartin@google.com>
On Fri, 10 Feb 2023 00:09:55 +0800, Martin Liu wrote:
> It's important to know reserved-mem information in mobile world
> since reserved memory via device tree keeps increased in platform
> (e.g., 45% in our platform). Therefore, it's crucial to know the
> reserved memory sizes breakdown for the memory accounting.
>
> This patch prints out reserved memory details during boot to make
> them visible.
>
> Below is an example output:
>
> [ 0.000000] OF: reserved mem: 0x00000009f9400000..0x00000009fb3fffff ( 32768 KB ) map reusable test1
> [ 0.000000] OF: reserved mem: 0x00000000ffdf0000..0x00000000ffffffff ( 2112 KB ) map non-reusable test2
> [ 0.000000] OF: reserved mem: 0x0000000091000000..0x00000000912fffff ( 3072 KB ) nomap non-reusable test3
>
> Signed-off-by: Martin Liu <liumartin@google.com>
> ---
> Changes in V2:
> -- instead of using debugfs, just print them out during boot
>
> drivers/of/of_reserved_mem.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
Applied, thanks!
prev parent reply other threads:[~2023-02-15 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 16:09 Martin Liu
2023-02-15 18:19 ` Rob Herring [this message]
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=167648517621.362040.7176595866897785827.robh@kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liumartin@google.com \
--cc=minchan@kernel.org \
--cc=robh+dt@kernel.org \
--cc=surenb@google.com \
--cc=tkjos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®