From: Nathan Lynch <nathanl@linux.ibm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: qemu boot log difference today
Date: Mon, 13 Feb 2023 23:19:43 -0600 [thread overview]
Message-ID: <878rh0aknk.fsf@linux.ibm.com> (raw)
In-Reply-To: <20230214143150.7c7fdd05@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> writes:
>
> Today's qemu boot log shows 256k extra in reserved memory:
>
> - Memory: 2046080K/2097152K available (14720K kernel code, 2944K rwdata, 18048K rodata, 5184K init, 1431K bss, 51072K reserved, 0K cma-reserved)
> + Memory: 2045824K/2097152K available (14720K kernel code, 2944K rwdata, 18048K rodata, 5184K init, 1439K bss, 51328K reserved, 0K cma-reserved)
>
> I don't know what has caused this.
Assuming it's pseries, it's the RTAS work area allocator reserving the
memory.
43033bc62d34 powerpc/pseries: add RTAS work area allocator
next prev parent reply other threads:[~2023-02-14 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 3:31 linux-next: qemu boot log difference today Stephen Rothwell
2023-02-14 5:19 ` Nathan Lynch [this message]
2023-02-14 6:12 ` Stephen Rothwell
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=878rh0aknk.fsf@linux.ibm.com \
--to=nathanl@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=sfr@canb.auug.org.au \
/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