All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <Yinghai.Lu@Sun.COM>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATCH] x86_64: fix comments in vmlinux_64.lds
Date: Thu, 31 Jan 2008 11:12:05 -0800	[thread overview]
Message-ID: <200801311112.05409.yinghai.lu@sun.com> (raw)
In-Reply-To: <20080131123503.GG12571@elte.hu>

On Thursday 31 January 2008 04:35:03 am Ingo Molnar wrote:
> 
> * Yinghai Lu <Yinghai.Lu@Sun.COM> wrote:
> 
> >  ENTRY(startup_64)
> >  SECTIONS
> >  {
> > -	/* Be careful parts of head_64.S assume startup_64 is at
> > +	/* Be careful parts of head_64.S assume startup_32 is at
> >  	 * address 0.
> >  	 */
> >  	. = 0;
> 
> but this linker script rule is about startup_64, not about startup_32.
> 
> startup_32 does exist on 64-bit too (and is 32-bit code), but it's 
> linked to a different address that is not 0:
> 
>  ffffffff806c23c0 r startup_32
> 
> startup_64 is at offset 0:
> 
>  ffffffff80200000 T startup_64
> 
> So your patch looks wrong to me.

there are several startup_32 in 64 bit
1. one is for bzImage, it is arch/x86/boot/compressed/head_64.S, and it said startup_64 will at 0x200. that what i mean
2. one is vmlinux in linux-2.6/ , it is in arch/x86/kernel/trampoline_64.S  it is for AP trampoline and wake up. that is what you mean

actually there was another one in arch/x86_64/kernel/head_64.S, and it was removed when Eric made linux-2.6/vmlinux to be 64bit elf. 

So that patch is needed.

YH


      reply	other threads:[~2008-01-31 18:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  7:48 PATCH] x86_64: fix comments in vmlinux_64.lds Yinghai Lu
2008-01-31 12:35 ` Ingo Molnar
2008-01-31 19:12   ` Yinghai Lu [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=200801311112.05409.yinghai.lu@sun.com \
    --to=yinghai.lu@sun.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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.