linux-kernel - Re: EFI e820 map handling

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:	Thu, 9 Aug 2007 22:11:33 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Andi Kleen" <ak@...e.de>
Cc:	"Huang, Ying" <ying.huang@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: EFI e820 map handling

On 8/9/07, Andi Kleen <ak@...e.de> wrote:
>
> Hallo,
>
> I thought a bit about the zero page problem. I really would prefer to not
> having it used in a boot loader right now because it's not extensible anymore
> when external users start (ab)using it.
>
> When I asked for separate EFI->e820 functions I was really thinking
> of the kernel to do the conversion; not the boot loader.
>
> Could you move that code into the kernel early boot code please?
> e.g. on x86-64 it could be in head64.c.  It could stuff the result
> into the zero page to pass it cleanly on without special cases later.
>
> On i386 a head32.c that runs before start_kernel() could be also
> introduced for this.
>
> As long as it's localized there it is fine.
>
> This would also allow to define new private e820 types and extend
> the string decoding in e820; so that dmesg will correctly contain
>
> EFI: ....
>
> instead of
>
> BIOS-e820: ...
>

How about elilo to load freebsd or opensolaris?

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