linux-kernel - Re: [tip:x86/kbuild] x86: unify arch/x86/boot/compressed/vmlinux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <49F5D70F.6070309@zytor.com>
Date:	Mon, 27 Apr 2009 09:02:23 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
	torvalds@...ux-foundation.org, sam@...nborg.org,
	tglx@...utronix.de, mingo@...e.hu
CC:	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/kbuild] x86: unify arch/x86/boot/compressed/vmlinux_*.lds

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/