* EFI e820 map handling
@ 2007-08-09 10:06 Andi Kleen
2007-08-10 5:11 ` Yinghai Lu
2007-08-10 13:17 ` huang ying
0 siblings, 2 replies; 4+ messages in thread
From: Andi Kleen @ 2007-08-09 10:06 UTC (permalink / raw)
To: Huang, Ying; +Cc: linux-kernel
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: ...
Thanks,
-Andi
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: EFI e820 map handling
2007-08-09 10:06 EFI e820 map handling Andi Kleen
@ 2007-08-10 5:11 ` Yinghai Lu
2007-08-10 7:55 ` Andi Kleen
2007-08-10 13:17 ` huang ying
1 sibling, 1 reply; 4+ messages in thread
From: Yinghai Lu @ 2007-08-10 5:11 UTC (permalink / raw)
To: Andi Kleen; +Cc: Huang, Ying, linux-kernel
On 8/9/07, Andi Kleen <ak@suse.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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: EFI e820 map handling
2007-08-10 5:11 ` Yinghai Lu
@ 2007-08-10 7:55 ` Andi Kleen
0 siblings, 0 replies; 4+ messages in thread
From: Andi Kleen @ 2007-08-10 7:55 UTC (permalink / raw)
To: Yinghai Lu; +Cc: Huang, Ying, linux-kernel
> How about elilo to load freebsd or opensolaris?
I don't know. How is that related? The current lilo can't load them either.
Supposedly they could write their own EFI boot loaders
-Andi
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: EFI e820 map handling
2007-08-09 10:06 EFI e820 map handling Andi Kleen
2007-08-10 5:11 ` Yinghai Lu
@ 2007-08-10 13:17 ` huang ying
1 sibling, 0 replies; 4+ messages in thread
From: huang ying @ 2007-08-10 13:17 UTC (permalink / raw)
To: Andi Kleen; +Cc: Huang, Ying, linux-kernel
On 8/9/07, Andi Kleen <ak@suse.de> wrote:
> 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.
I think there is more to be discussed than just EFI->e820 conversion.
We can discuss them in another thread.
Best Regards,
Huang Ying
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2007-08-10 13:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-09 10:06 EFI e820 map handling Andi Kleen
2007-08-10 5:11 ` Yinghai Lu
2007-08-10 7:55 ` Andi Kleen
2007-08-10 13:17 ` huang ying
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox