Re: [PATCH 5/5] x86_64 EFI support -v3: EFI document

[ebiederm@xmission.com (Eric W. Biederman)]

Andi Kleen <ak@suse.de> writes:

>> 
>> This is the classic skip the 16bit code and enter the kernel
>> in 32bit mode filling in the fields that the 16bit mode code would
>> have filled in the same way approach.
>
> kexec can use it because it's in tree.

Not the part that actually uses it.

> But I don't think using it by out of tree stuff is a good idea.
>
> e.g. assuming we need a new field. How would we extend this?
> There is no version number or anything to detect this.
>
> For in tree code it can be just updated. But weirdo-EFI-boot loader
> cannot.

So far the logic has been.

Inspect bzImage.  And get boot protocol version.
If field we need for returning data is not supported do not give
data.  Or something like that.  Usually the fields always exist
and you can just fill them in and we only append to the boot
protocol structure.

In practice this has been working for the last 7 years or so,
for EFI, and LinuxBIOS, and kexec, and Gujin and I don't remember what
else.

It isn't the prettiest thing in the world but it works and everybody
who needs it uses it.  Which tend to be the important parts for a
standard.

Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/