lkml.org 
[lkml]   [2008]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 4/8] x86 boot: allow overlapping ebda and efi memmap memory ranges
Paul Jackson wrote:
>
> The question to me is this. Are there PCs which (1) need such a safety
> reservation of an ebda area -and- (2) boot with EFI enabled? I am not
> asking if there -could- be (in the abstract, there certainly is no law
> of government or physics prohibiting such). Rather I am asking as a
> practical matter if there is, or is likely to be, such PCs "in the wild."
>
> The safety reservation of this ebda area is a hack. As hacks go, it is
> a rather gentle hack, but still it is a hack. As such, it is to be
> avoided unless there is a practical need. Some non-efi old PCs have that
> need - no debate there.
>
> Should we perpeturate this (gentle) hack for EFI systems as well?
>

We *are* going to have similar hacks. That's not a question. At this
point, the live pool of EFI systems is functionally zero, so it's
pointless to try to draw conclusions from the live pool (the little I
have heard about the incoming set of EFI machines make me think the
problems we've had with BIOS will look like child's play compared to the
EFI braindamages we'll have to suffer.)

Perpetuating this hack will cost a few kilobytes of memory on machines
which may not care. *Not* perpetuating may save a few kilobytes on
machines which may cause odd behaviours that only are noticeable when
you, say, boot from one OS into another.

Guess which option I think is saner.

-hpa


\
 
 \ /
  Last update: 2008-06-16 19:49    [W:0.447 / U:0.092 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site