Rusty Russell <[email protected]> writes:
> Hi Eric,
>
> Well, I certainly don't recall that (that's not to say that someone
> didn't say it). Trying to meet the requirements of Xen, VMI and other
> future hypervisors lead to an awkward result; this is the main reason I
> started on lguest, so we'd have a simple example in front of us to say
> "do it this way".
>
> (It's not certain that anyone else will ever use this code, but we
> should *try* IMHO).
Ok. So the purpose of lguest is to be an experimental platform and
as much as possible be a good example.
>> Before lguest. Thank you very much. This code should never ever
>> have been in a stable kernel. It is a very ill conceived interface.
>
> I disagree. It was *not* obvious how paravirt kernels should boot.
> Lguest, for example, copied Xen's "set up kernel pagetables already"
> design decision, which now seems wrong. But it was the example we had.
Makes some sense. There was a bit of experience with booting kernels
without doing 16bit BIOS calls in nearly this way outside the paravirt
world though.
>> And frankly I don't think lguest should be merged until we are as
>> close to certain as human beings can get that have the ABI reviewed
>> and sorted out. ABIs unfortunately are very very hard to change.
>
> I think you misunderstand lguest. I agree with this sentiment
> completely: this is *why* lguest doesn't have an ABI. It's all in-tree,
> so it can simply be changed. There's no guarantee that running
> different kernels as guest and host will work.
Reasonable. Just so long as it is hidden under CONFIG_EXPERIMENTAL
And that people will know that mixing and matching is a problem.
Someday I might have to tell the story of the challenge of getting
the kexec on panic code path to all mixing and matching of kernels.
> Maybe later the ABI will nail down, but the last year of hacking on
> various hypervisors has shown it's folly to try to get it right now. We
> need to play a lot first.
>
> Hope that clarifies!
For lguest at least.
The delicate part right now is that lguest is attempting to use the
standard kernel entry point which does have a fixed ABI.
If lguest uses that entry point in a hard to maintain way it provides
a bad example, and it potentially leads to other problems. So I
really don't want to see the bad example happen, especially if the
code in the bad example is as general as it is today.
That said we have two practical short term solutions.
- A separate entry point made advertised with an ELF note like
Xen is currently doing.
- We reserve a type field in the first 2K of the boot param area
and if that type is lguest we immediately branch to your code.
Reserving the type field is a subset of what we are looking at for
the next rev of the boot protocol that will handle this clearly.
We have enough in flight work for cleaning up the booting of arch/i386
that I don't believe we can have a complete solution before the merge
window closes. At best we can get a minor rev and reserve the fields
it looks like we will need in head.S
Frankly I think the least risk of problems comes from just doing a
separate entry point for lguest for now. It means we don't even have
to touch the common code path and later dropping will be trivially
lguest specific, and certain to not break anything else.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
