From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
torvalds@linux-foundation.org, sam@ravnborg.org,
tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/kbuild] x86: unify arch/x86/boot/compressed/vmlinux_*.lds
Date: Mon, 27 Apr 2009 09:02:23 -0700 [thread overview]
Message-ID: <49F5D70F.6070309@zytor.com> (raw)
In-Reply-To: <tip-51b26ada79b605ed709ddcedbb6012e8f8e0ebed@git.kernel.org>
tip-bot for Linus Torvalds wrote:
>
> Also, notice the comment in the unified vmlinux.lds.S talks about
> "head_64" and "startup_32" which is an odd and incorrect mix, but that was
> actually what the old 64-bit only lds file had, so the confusion isn't
> new, and now that mixing is arguably more accurate thanks to the
> vmlinux.lds.S file being shared between the two cases ;)
>
It's correct, IIRC; the 64-bit code has startup_32 and startup_64, since
it is entered in 32-bit mode; startup_32 marks the entrypoint in the
beginning of the file.
hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
parent reply other threads:[~2009-04-27 16:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-51b26ada79b605ed709ddcedbb6012e8f8e0ebed@git.kernel.org>]
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=49F5D70F.6070309@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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