From: Greg Ungerer <gerg@snapgear.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org, uclinux-dev@uclinux.org,
Greg Ungerer <gerg@uclinux.org>
Subject: Re: [PATCH] m68k: print memory layout info in boot log
Date: Sat, 22 Oct 2011 07:36:56 +1000 [thread overview]
Message-ID: <4EA1E5F8.7080108@snapgear.com> (raw)
In-Reply-To: <CAMuHMdWYBDd+rVe4FF7TYhNcyr_na09u8csVvw7L19Ry9Y2GWA@mail.gmail.com>
Hi Geert,
On 10/22/2011 12:56 AM, Geert Uytterhoeven wrote:
> On Fri, Oct 21, 2011 at 09:07,<gerg@snapgear.com> wrote:
>> Output a table of the kernel memory regions at boot time.
>> This is taken directly from the ARM architecture code that does this.
>> The table looks like this:
>
> arch/m68k/mm/init_mm.c: In function æprint_memmapÆ:
> arch/m68k/mm/init_mm.c:108: error: æ_sbssÆ undeclared (first use in
> this function)
> arch/m68k/mm/init_mm.c:108: error: (Each undeclared identifier is
> reported only once
> arch/m68k/mm/init_mm.c:108: error: for each function it appears in.)
> arch/m68k/mm/init_mm.c:108: error: æ_ebssÆ undeclared (first use in
> this function)
This patch relies on one I posted a little while back:
http://www.spinics.net/lists/linux-m68k/msg04054.html
which is currently in linux-next. So I am getting a little ahead
of things here I guess :-)
>> + á á á printk(KERN_NOTICE "Virtual kernel memory layout:\n"
>
> pr_notice
Yep, I will change that.
>> + á á á á á á á " á ávector á: 0x%08lx - 0x%08lx á (%4ld kB)\n"
>> + á á á á á á á " á ákmap á á: 0x%08lx - 0x%08lx á (%4ld MB)\n"
>> + á á á á á á á " á ávmalloc : 0x%08lx - 0x%08lx á (%4ld MB)\n"
>> + á á á á á á á " á álowmem á: 0x%08lx - 0x%08lx á (%4ld MB)\n"
>> + á á á á á á á " á á á.init : 0x%p" " - 0x%p" " á (%4d kB)\n"
>> + á á á á á á á " á á á.text : 0x%p" " - 0x%p" " á (%4d kB)\n"
>> + á á á á á á á " á á á.data : 0x%p" " - 0x%p" " á (%4d kB)\n"
>> + á á á á á á á " á á á.bss á: 0x%p" " - 0x%p" " á (%4d kB)\n",
>
> KiB, MiB?
Yep, thats better. I'll change that too. Thanks.
Regards
Greg
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg@snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close, FAX: +61 7 3891 3630
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2011-10-21 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-21 7:07 [PATCH] m68k: print memory layout info in boot log gerg
2011-10-21 14:56 ` Geert Uytterhoeven
2011-10-21 21:36 ` Greg Ungerer [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=4EA1E5F8.7080108@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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