From: "Magnus Damm" <magnus.damm@gmail.com>
To: "Chase Venters" <chase.venters@clientec.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: .exit.text section in vmlinux
Date: Mon, 3 Jul 2006 16:31:19 +0900 [thread overview]
Message-ID: <aec7e5c30607030031p2cb27c0bt3486740a923a61e0@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0606301111370.21298@turbotaz.ourhouse>
On 7/1/06, Chase Venters <chase.venters@clientec.com> wrote:
> On Fri, 30 Jun 2006, Magnus Damm wrote:
> > The linker script arch/i386/kernel/vmlinux.lds.S mentions the following:
> >
> > /* .exit.text is discard at runtime, not link time, to deal with references
> > from .altinstructions and .eh_frame */
>
> .altinstructions is for alternatives code (code that is rewritten at
> runtime based on some factor such as UP-vs-SMP). .eh_frame has call
> framing information used for unwinding. I think it's copied into the
> vsyscall page (not entirely familiar with this mechanism though).
Thanks for clarifying.
> > The text above seems to answer my question, but I cannot say I fully
> > understand the comment. I'd appreciate if someone could explain a bit
> > more if possible.
> >
> > Ok, so the section should be discarded at runtime. Sounds ok. But
> > where in the code is this section discarded? -ENOSYS?
>
> When you see "Freeing unused kernel memory", the memory between
> __init_begin and __init_end (as marked in vmlinux.ld.S) is released. See
> arch-specific mm/init.c.
Oh, I see. It looks like things are working as expected then. Thank you!
Cheers,
/ magnus
prev parent reply other threads:[~2006-07-03 7:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 6:54 Magnus Damm
2006-06-30 16:31 ` Chase Venters
2006-07-03 7:31 ` Magnus Damm [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=aec7e5c30607030031p2cb27c0bt3486740a923a61e0@mail.gmail.com \
--to=magnus.damm@gmail.com \
--cc=chase.venters@clientec.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®