This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: A proposal - binary

* Andrew Morton (akpm@xxxxxxxx) wrote:
> I must confess that I still don't "get" paravirtops.  AFACIT the VMI
> proposal, if it works, will make that whole layer simply go away.  Which
> is attractive.  If it works.

Paravirtops is simply a table of function which are populated by the
hypervisor specific code at start-of-day.  Some care is taken to patch
up callsites which are performance sensitive.  The main difference is
the API vs. ABI distinction.  In paravirt ops case, the ABI is defined at
compile time from source.  The VMI takes it one step further and fixes
the ABI.  That last step is a big one.

There are two basic issues. 1) what is the interface between the kernel
and the glue to a hypervisor. 2) how does one call from the kernel into
the glue layer.

Getting bogged down in #2, the details of the calling convention, is a
distraction from the real issue, #1.  We are trying to actually find an
API that is useful for multiple projects.  Paravirt_ops gives the
flexibility to evolve the interface.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>