Re: ABI coupling to hypervisors via CONFIG_PARAVIRT

[Ingo Molnar <mingo@elte.hu>]

* Linus Torvalds <torvalds@linux-foundation.org> wrote:

> If we change paravirt_ops to be higher-level ops (as we should), yes, 
> the paravirt->VMI layer needs to be extended to have the 
> "higher->lower" translation. But at no point did we break the 
> hypervisor.

hm. So your point is that VMI is in essence a Turing machine (a 
near-complete one)? No matter what redesign we do on the Linux side, the 
VMI paravirt_ops will always be able to adopt to it? If that is the case 
then my ABI worries would indeed be wrong and i'd owe Zach a big fat 
apology [and more] for my flames ;-)

but what if the transformation is not just a top-down transformation, 
but something more conceptual, introducing something that VMI does not 
cover today, like: 'elimination of the APIC concept from guest mode 
(replacing it with a virtual interrupt controller)', or 'elimination of 
the concept of IRQ vectors from guest mode (virtual irq controller)'. Or 
'elimination of pagetables stored in the guest (all paravirt hooks would 
be vma-based)'?

but ... maybe because VMI is so lowlevel and covers /all/ of x86 today, 
it will always be able to emulate whatever different concept we can come 
up with? Do we really know this absolutely sure?

	Ingo