linux-kernel - Re: [PATCH v2 03/13] x86: Add macro for 64bit entry startup

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: <CAE9FiQVMBBHoi4pr2VGo8jWbqPpOzt62w51Rk-v=RMxddJkdSg@mail.gmail.com>
Date:	Tue, 20 Nov 2012 16:32:09 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org, Matt Fleming <matt.fleming@...el.com>
Subject: Re: [PATCH v2 03/13] x86: Add macro for 64bit entry startup_64

On Tue, Nov 20, 2012 at 4:28 PM, H. Peter Anvin <hpa@...or.com> wrote:
> On 11/20/2012 04:20 PM, Yinghai Lu wrote:
>>
>>> relocatable_kernel really should have been a flag, but it is now defined as
>>> a comparison with zero.  As such, and in an effort to minimize the growth of
>>> struct setup_header (it is limited to little over 128 bytes long) I suggest
>>> we redefine the 16-byte field at offset 0x236 as a new flags field.  We
>>> still only need one flag, though.

ok will use 0x236.

Thanks

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