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:	Wed, 23 Jan 2008 16:07:55 +0800
From:	"Huang, Ying" <ying.huang@...el.com>
To:	Paul Jackson <pj@....com>
Cc:	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	hpa@...or.com, ak@...e.de, adaplas@....net,
	linux-kernel@...r.kernel.org
Subject: Re: Could you please merge the x86_64 EFI boot support patchset?

On Wed, 2008-01-23 at 01:46 -0600, Paul Jackson wrote:
> Huang wrote:
> > This patchset has been merged into Linux 2.6.24.
> 
> Excellent.
> 
> > Unfortunately, the new EFI support patches do not use EFI memory map for
> > system boot up ...  So, I think the resolution for your problem is the
> > "struct setup_data" mechanism proposed by H. Peter Anvin.
> 
> So you're saying that the EFI in the kernel now still won't support more
> than 128 or so chunks of memory in the boottime memory map, because it
> still goes via the legacy E820h memory map code?

The kernel with EFI support can not support more than 128 or so chunks
of memory. Because the EFI memory map is converted to E820 memory map in
boot-loader (such as elilo).

> I'll have to study the code more and give it a try.
> 
> Are you optimistic that some variation of H. Peter Anvin's "struct
> setup_data" mechanism will make it into 2.6.25 or thereabouts?

I think it may be merged into 2.6.26.

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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ