linux-kernel - Re: [RFC -mm 0/2] i386/x86_64 boot: 32-bit boot protocol

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]

Date:	Mon, 17 Sep 2007 16:47:35 +0800
From:	"Huang, Ying" <ying.huang@...el.com>
To:	Andi Kleen <ak@...e.de>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	akpm@...ux-foundation.org, Yinghai Lu <yhlu.kernel@...il.com>,
	Chandramouli Narayanan <mouli@...ux.intel.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC -mm 0/2] i386/x86_64 boot: 32-bit boot protocol

On Mon, 2007-09-17 at 10:40 +0200, Andi Kleen wrote:
> On Monday 17 September 2007 10:26:12 Huang, Ying wrote:
> > For machine with some new BIOS other than legacy BIOS, such as EFI,
> > LinuxBIOS, etc, and kexec, the 16-bit real mode setup code in kernel
> > based on legacy BIOS can not be used, so a 32-bit boot protocol need
> > to be defined.
> 
> The patch doesn't seem to be what you advertise in the description.
> Can you start with a patch that just implements the new boot protocol
> parsing for better review? The EFI code should be all in separate 
> patches.
> -Andi

The real contents of 32-bit boot protocol patch is is in another 2 mails
with the title:

[RFC -mm 1/2] i386/x86_64 boot: setup data
[RFC -mm 2/2] i386/x86_64 boot: document for 32 bit boot protocol

The EFI patch in this mail is just an example of 32-bit boot protocol
usage.

Best Regards,
Huang Ying
-
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/