linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org,
	Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>
Subject: Re: __init, __openfirmware, etc...
Date: Sun, 3 Jan 1999 10:42:28 +0100	[thread overview]
Message-ID: <19990103104228.031876@smtp.calvacom.fr> (raw)
In-Reply-To: <Pine.LNX.4.02.9901022154330.2266-100000@cassiopeia.home>


On Sat, Jan 2, 1999, Geert Uytterhoeven <geert@geert.cs.kuleuven.ac.be> wrote:

>__init sections are indeed removed after kernel initialisation. The
other ones
>are removed depending on the dynamic run type of the machine, e.g. __pmac
>sections are removed on PReP, and so on. Saves quite some valuable
unswappable
>kernel memory.c

Ok. Do you know what happens to static datas declared within an __init
function ? Is it removed to ? I have a function that use a static array
for putting permanent "override" values for part of the device tree and
this array must not be removed. Should I put the static array out of the
function too or will this remove mecanism avoid bss sections ?

-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>



[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]

  reply	other threads:[~1999-01-03  9:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-30 10:37 grackle, patches, MMU, Benjamin Herrenschmidt
1998-12-30 11:22 ` Geert Uytterhoeven
1998-12-30 11:35   ` Benjamin Herrenschmidt
1998-12-30 13:21     ` Geert Uytterhoeven
1998-12-31 21:52 ` Cort Dougan
1998-12-31 22:24   ` Benjamin Herrenschmidt
1998-12-31 22:48     ` Cort Dougan
1999-01-02 15:24       ` __init, __openfirmware, etc Benjamin Herrenschmidt
1999-01-02 20:55         ` Geert Uytterhoeven
1999-01-03  9:42           ` Benjamin Herrenschmidt [this message]
1999-01-03 15:04             ` Geert Uytterhoeven
1999-01-01 20:45     ` real-root-dev patch for vger Brad Midgley
1999-01-02 20:54       ` Geert Uytterhoeven
1999-01-03 22:24         ` Brad Midgley
1999-01-03 22:38           ` Geert Uytterhoeven
1999-01-04 10:29             ` Andreas Schwab

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=19990103104228.031876@smtp.calvacom.fr \
    --to=bh40@calva.net \
    --cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).