linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Where does ppc define __start___ksymtab?
Date: Thu, 03 Aug 2000 22:18:36 +1000	[thread overview]
Message-ID: <31728.965305116@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Thu, 03 Aug 2000 14:01:44 +0200." <Pine.HPX.4.10.10008031350200.9070-100000@gra-ux1.iram.es>


On Thu, 3 Aug 2000 14:01:44 +0200 (METDST),
Gabriel Paubert <paubert@iram.es> wrote:
>On Thu, 3 Aug 2000, Keith Owens wrote:
>> If we want anything in the kernel then we put it there, and say where
>> we want it.  Anything not explicitly listed is discarded.  I just did
>> this with ix86 and vmlinux shrank by 9K, mainly in .bss.  It would not
>> boot afterwards so obviously some part of that 9K is required but right
>> now it works by some "magic" storing the unknown sections.  I'm going
>> to track down which sections are not being explicitly placed.
>
>I have trouble parsing this, since the bss by definition does not occupy
>any space in vmlinux.

It is wierd.  Even though arch/i386/vmlinux.lds contains
".bss : { *(.bss) }", something extra is getting stored in .bss.  The
data has the same attributes as .bss, ALLOC only, alignment 2**5 but
its section name is not ".bss".  Adding

  .note : { *(.note) }
  .rest : { *(*) }

to the end of an otherwise untouched arch/i386/vmlinux.lds changes
vmlinux from this

 14 .bss          0003bb8c  c02a6c40  c02a6c40  001a7c40  2**5
                  ALLOC
 15 .comment      000044a0  00000000  00000000  001a7c40  2**0
                  CONTENTS, READONLY
 16 .note         00001680  c02e27cc  c02e27cc  001ac0e0  2**0
                  CONTENTS, READONLY

to this

 14 .bss          00014240  c02a6c40  c02a6c40  001a7c40  2**5
                  ALLOC
 15 .comment      000044a0  00000000  00000000  001a7c40  2**0
                  CONTENTS, READONLY
 16 .note         00001680  c02bae80  c02bae80  001ac0e0  2**0
                  CONTENTS, READONLY
 17 .rest         0002794c  c02bae80  c02bae80  001a7c40  2**5
                  ALLOC

Which is a lot more than 9K of unknown data.  I was looking at the on
disk size which contains the .note section, however removing that
should only shrink by 4K so I do not understand why vmlinux shrank by
9K.  The final step on i386 removes .note and
.comment from the bootable kernel anyway.

I'm trying to track down where the extra .bss like data is coming from.
I will mail the list when I find something.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-03 12:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-01  6:40 Where does ppc define __start___ksymtab? Keith Owens
2000-08-02 20:18 ` Geert Uytterhoeven
2000-08-03 11:28   ` Gabriel Paubert
2000-08-03 11:40   ` Keith Owens
2000-08-03  6:13 ` Paul Mackerras
2000-08-03  8:03   ` Keith Owens
2000-08-03  9:58     ` Gabriel Paubert
2000-08-03 11:43       ` Keith Owens
2000-08-03 12:01         ` Gabriel Paubert
2000-08-03 12:18           ` Keith Owens [this message]
2000-08-03 12:31             ` Gabriel Paubert
2000-08-03 12:27           ` Keith Owens
2000-08-03 13:08           ` Franz Sirl

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=31728.965305116@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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).