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, 23 Jun 2008 01:53:26 -0500
From:	Paul Jackson <pj@....com>
To:	"Huang, Ying" <ying.huang@...el.com>
Cc:	mingo@...e.hu, hpa@...or.com, andi@...stfloor.org,
	mingo@...hat.com, tglx@...utronix.de, linux-kernel@...r.kernel.org,
	yhlu.kernel@...il.com
Subject: Re: [PATCH] x86 boot: Pass E820 memory map entries more than 128
 via linked list of setup data

Huang Ying wrote:
> With this patch, your previous patch:
> 
> x86 boot: add code to add BIOS provided EFI memory entries to kernel
> 
> is not necessary, so can be reversed.
> 
> What do you think about that?

... the same thing I thought about it when you asked this question
last month, in post http://lkml.org/lkml/2008/5/26/307.

Please see my reply in http://lkml.org/lkml/2008/5/28/59.
It was lengthy and carefully researched, so I won't repeat
it here.

In short, we still need it.  The key kernel routine that adds
additional EFI entries to the existing E820 map is just 20 or so
fairly easy lines.  We agree that it doesn't handle some of what your
more extended work with a linked list of setup data handles (such as
additional EDD entries), but it does handle additional memory map
(node) entries using the existing data structure interface between
the firmware and kernel.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@....com> 1.940.382.4214
--
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