From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: linux-arch@vger.kernel.org, macro@linux-mips.org,
linux-mips@linux-mips.org
Subject: Re: [PATCH 2/2] MIPS: vmlinux.lds.S: handle .{init,exit}.bss sections
Date: Mon, 03 Dec 2007 22:46:14 +0100 [thread overview]
Message-ID: <47547926.5060806@gmail.com> (raw)
In-Reply-To: <617E1C2C70743745A92448908E030B2A030FE4C2@scsmsx411.amr.corp.intel.com>
Luck, Tony wrote:
> + /*
> + * We keep init/exit bss sections here to have only one
> + * segment to load. Note that .bss.exit is also discarded
> + * at runtime for the same reason as above.
> + */
> + .exit.bss : {
> + *(.bss.exit)
> + }
>
> This change would also require an audit of the bootloader or early
> kernel initialization code (whichever handles zeroing of .bss space)
I think the kernel doesn't rely on the bootloader for clearing bss.
> to make sure that it understands that the kernel will now have an
> extra block of memory that needs to be cleared. Perhaps nothing
> needs to be done if the code already handled the general case of
> loading an ELF binary with some sections that have an in-memory
> size bigger than the on-disk size. But worth looking at in case
> the code makes an assumption about what needs to be zeroed.
>
For MIPS case, there is normally no extra block of memory to
clear. [__bss_start, __bss_stop] range still includes the whole memory
block to clear. So there's no need to modify any other code.
Franck
prev parent reply other threads:[~2007-12-03 21:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 21:13 [RFC] Yet another __init annotation: __initbss Franck Bui-Huu
2007-12-01 21:13 ` [PATCH 1/2] Yet another __initxxx annotations: __initbss/__exitbss Franck Bui-Huu
2007-12-01 23:18 ` Russell King
2007-12-02 21:36 ` Franck Bui-Huu
2007-12-01 21:13 ` [PATCH 2/2] MIPS: vmlinux.lds.S: handle .{init,exit}.bss sections Franck Bui-Huu
2007-12-03 17:00 ` Luck, Tony
2007-12-03 17:00 ` Luck, Tony
2007-12-03 21:46 ` Franck Bui-Huu [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=47547926.5060806@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=tony.luck@intel.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