public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Jan Beulich <jbeulich@novell.com>
Cc: Andi Kleen <ak@muc.de>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>,
	Ian Campbell <Ian.Campbell@xensource.com>
Subject: Re: [PATCH] x86_64: Some vmlinux.lds.S cleanups
Date: Thu, 26 Oct 2006 11:12:41 -0400	[thread overview]
Message-ID: <20061026151241.GC11284@in.ibm.com> (raw)
In-Reply-To: <4540D9CF.76E4.0078.0@novell.com>

On Thu, Oct 26, 2006 at 03:52:47PM +0200, Jan Beulich wrote:
> >>> Vivek Goyal <vgoyal@in.ibm.com> 26.10.06 15:44 >>>
> >On Thu, Oct 26, 2006 at 08:08:21AM +0100, Jan Beulich wrote:
> >> I was about to ack it when I saw that you left .bss in init - that doesn't seem
> >> too good an idea... Jan
> >> 
> >
> >Should I create a separate program header say "bss" for .bss section? Last
> >time when I suggested it you said there is no need to create a separate
> >program header for bss.
> 
> No, I continue to think .bss naturally belongs at the end of the data segment.
> 

Only disadvantage of this is that .bss becomes part of the compressed data
and size of vmlinux.bin and bzImage increases.

OTOH, all the sections being mapped in segment "user" are also effectively
data only. isn't it? So .bss coming after that would make sense.

Thanks
Vivek

      reply	other threads:[~2006-10-26 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24 21:01 [PATCH] x86_64: Some vmlinux.lds.S cleanups Vivek Goyal
2006-10-26  7:08 ` Jan Beulich
2006-10-26 13:44   ` Vivek Goyal
2006-10-26 13:52     ` Jan Beulich
2006-10-26 15:12       ` Vivek Goyal [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=20061026151241.GC11284@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=Ian.Campbell@xensource.com \
    --cc=ak@muc.de \
    --cc=jbeulich@novell.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