All of lore.kernel.org
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-mips <linux-mips@linux-mips.org>
Subject: Re: [RFC] Add __initbss section
Date: Sun, 14 Oct 2007 21:52:42 +0200	[thread overview]
Message-ID: <4712738A.5000703@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64N.0710111307180.16370@blysk.ds.pg.gda.pl>

Maciej W. Rozycki wrote:
> On Thu, 11 Oct 2007, Franck Bui-Huu wrote:
> 
>> and the kernel image is bigger after the patch is applied !
>>
>> $ ls -l vmlinux*
>> -rwxrwxr-x 1 fbuihuu fbuihuu 2503324 2007-10-11 11:41 vmlinux*
>> -rwxrwxr-x 1 fbuihuu fbuihuu 2503264 2007-10-11 11:41 vmlinux~old*
>>
>> Could anybody explain me why ? The time is missing and I probably
>> couldn't investigate into this until this weekend. 
> 
>  I guess for a bss-type section you want to use something like:
> 
> 	.section .init.bss,"aw",@nobits
> 

Sorry but I'm missing your point here. This indeed should be added
for assembler code but I don't see how it's related with the kernel
image size difference I was seeing.

> 
>  Well, there should be no need for an extra segment -- just rearrange the 
> order of the sections in the linker script appropriately.  You should 
> probably add __exitbss for consistency too.  You can make all the three 
> sections adjacent so that no separate initialisation is required.
> 

I'll do that.

		Franck

  reply	other threads:[~2007-10-14 19:53 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-11  9:52 [RFC] Add __initbss section Franck Bui-Huu
2007-10-11  9:54 ` [PATCH 1/2] Add .init.bss section Franck Bui-Huu
2007-10-11  9:58 ` [PATCH 2/2] Add .init.bss section for MIPS Franck Bui-Huu
2007-10-11 12:44 ` [RFC] Add __initbss section Ralf Baechle
2007-10-11 13:35   ` Maciej W. Rozycki
2007-10-11 14:00     ` Ralf Baechle
2007-10-11 14:49       ` Maciej W. Rozycki
2007-10-14 19:42   ` Franck Bui-Huu
2007-10-15 16:01     ` Ralf Baechle
2007-10-16  8:33       ` Franck Bui-Huu
2007-10-11 13:19 ` Maciej W. Rozycki
2007-10-14 19:52   ` Franck Bui-Huu [this message]
2007-10-15 12:19     ` Maciej W. Rozycki
2007-10-15 20:06       ` Franck Bui-Huu
2007-10-16 10:29         ` Maciej W. Rozycki
2007-10-18 20:28           ` Franck Bui-Huu
2007-10-19 11:59             ` Maciej W. Rozycki
2007-11-04  8:29               ` Franck Bui-Huu
2007-11-05 12:38                 ` Maciej W. Rozycki
2007-11-05 20:32                   ` Franck Bui-Huu
2007-10-11 15:26 ` Thiemo Seufer
2007-10-11 16:16   ` Maciej W. Rozycki
2007-10-11 16:25     ` Ralf Baechle
2007-10-11 17:07       ` Maciej W. Rozycki
2007-10-11 16:39     ` Thiemo Seufer
2007-10-14 19:53   ` Franck Bui-Huu

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=4712738A.5000703@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@linux-mips.org \
    --cc=ralf@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.