linux-kernel - Re: [PATCH 32/33] x86_64: Relocatable kernel support

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <m1zmb6per0.fsf@ebiederm.dsl.xmission.com>
Date:	Sat, 04 Nov 2006 23:52:03 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"Yinghai Lu" <yinghai.lu@....com>
Cc:	"Andi Kleen" <ak@...e.de>, Horms <horms@...ge.net.au>,
	"Jan Kratochvil" <lace@...kratochvil.net>,
	"H. Peter Anvin" <hpa@...or.com>,
	"Magnus Damm" <magnus.damm@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 32/33] x86_64: Relocatable kernel support

"Yinghai Lu" <yinghai.lu@....com> writes:

> On 8/1/06, Eric W. Biederman <ebiederm@...ssion.com> wrote:
>> I guess I could take this in some slightly smaller steps.
>> But this does wind up with decompressor being 64bit code.
>
> Sorry to bring out the old mail.
>
> except reusing the uncompressor in 32bit, is there any reason that you
> removed startup_32 for vmlinux but keep startup_32 for bzImage?
>
> that will make vmlinux use 64bit boot loader only.

If you are booting a vmlinux you read the ELF header.  The ELF header
only describes the native mode.  Therefore no 32bit entry makes much sense.

bzImage is something else entirely.

Eric

-
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/