From: "Antonio Vargas" <windenntw@gmail.com>
To: "Chris Wright" <chrisw@sous-sol.org>,
"Andrew Morton" <akpm@osdl.org>,
"Jeremy Fitzhardinge" <jeremy@xensource.com>,
greg@kroah.com, zach@vmware.com, linux-kernel@vger.kernel.org,
torvalds@osdl.org, hch@infradead.org, rusty@rustcorp.com.au,
jlo@vmware.com, xen-devel@lists.xensource.com,
simon@xensource.com, ian.pratt@xensource.com, jeremy@goop.org
Subject: Re: A proposal - binary
Date: Fri, 4 Aug 2006 08:28:26 +0200 [thread overview]
Message-ID: <69304d110608032328r36bc0a6ase0a2dbf36d8cc519@mail.gmail.com> (raw)
In-Reply-To: <20060804054002.GC11244@sequoia.sous-sol.org>
On 8/4/06, Chris Wright <chrisw@sous-sol.org> wrote:
> * Andrew Morton (akpm@osdl.org) 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.
One feature I found missing at the paravirt patches is to allow the
user to forbid the use of paravirtualization of certain features (via
a bitmask on the kernel commandline for example) so that the execution
drops into the native hardware virtualization system. Such a feature
would provide a big upwards compatibility for the kernel<->hypervisor
system. The case for this would be needing to forcefully upgrade the
hypervisor due to security issues and finding out that the hypervisor
is incompatible at the paravirtualizatrion level, then the user would
be at least capable of continuing to run the old kernel with the new
hypervisor until the compatibility is reached again.
BTW, what is the recommended distro or kernel setup to help testing
the latest paravirt patches? I've got a spare machine (with no needed
data) at hand which could be put to good use.
--
Greetz, Antonio Vargas aka winden of network
next prev parent reply other threads:[~2006-08-04 6:28 UTC|newest]
Thread overview: 96+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 10:14 Zachary Amsden
2006-08-03 11:16 ` Arjan van de Ven
2006-08-03 12:16 ` Antonio Vargas
2006-08-03 15:17 ` Rik van Riel
2006-08-03 16:05 ` Chris Wright
2006-08-03 17:57 ` Zachary Amsden
2006-08-03 18:29 ` Antonio Vargas
2006-08-03 18:47 ` Zachary Amsden
2006-08-03 18:08 ` Zachary Amsden
2006-08-03 19:03 ` Greg KH
2006-08-03 19:14 ` Zachary Amsden
2006-08-03 19:36 ` Greg KH
2006-08-03 19:56 ` Dave Jones
2006-08-03 19:59 ` Greg KH
2006-08-03 20:25 ` Options depending on STANDALONE Adrian Bunk
2006-08-03 20:28 ` Greg KH
2006-08-03 20:41 ` Dave Jones
2006-08-03 23:40 ` [v4l-dvb-maintainer] " Trent Piepho
2006-08-05 10:51 ` Adrian Bunk
2006-08-06 11:18 ` Oliver Endriss
2006-08-13 16:36 ` Adrian Bunk
2006-08-14 21:15 ` Trent Piepho
2006-08-27 21:45 ` Adrian Bunk
2006-08-03 19:48 ` A proposal - binary linux-os (Dick Johnson)
2006-08-04 6:13 ` Jan Engelhardt
2006-08-03 21:03 ` Alan Cox
2006-08-03 13:21 ` Alan Cox
2006-08-03 20:29 ` Willy Tarreau
2006-08-03 21:12 ` Alan Cox
2006-08-03 21:27 ` Zachary Amsden
2006-08-03 15:35 ` Rik van Riel
2006-08-03 18:36 ` Zachary Amsden
2006-08-05 10:45 ` Pavel Machek
2006-08-06 22:45 ` Zachary Amsden
2006-08-06 22:59 ` Greg KH
2006-08-08 0:12 ` Pavel Machek
2006-08-08 0:42 ` Zachary Amsden
2006-08-09 7:43 ` Pavel Machek
2006-08-03 19:06 ` Greg KH
2006-08-03 19:26 ` Zachary Amsden
2006-08-03 20:01 ` Greg KH
2006-08-03 21:41 ` Zachary Amsden
2006-08-03 22:33 ` Alan Cox
2006-08-03 22:30 ` Greg KH
2006-08-03 22:49 ` Zachary Amsden
2006-08-03 22:31 ` Zachary Amsden
2006-08-03 23:30 ` Alan Cox
2006-08-03 23:40 ` Zachary Amsden
2006-08-04 10:21 ` Alan Cox
2006-08-04 14:34 ` Theodore Tso
2006-08-05 0:06 ` Paul Mackerras
2006-08-04 8:56 ` Christoph Hellwig
2006-08-04 2:52 ` Jeremy Fitzhardinge
2006-08-04 4:18 ` Andrew Morton
2006-08-04 5:04 ` Rusty Russell
2006-08-04 5:53 ` Andrew Morton
2006-08-04 7:04 ` Rusty Russell
2006-08-04 7:21 ` Andrew Morton
2006-08-04 8:29 ` Rusty Russell
2006-08-04 16:57 ` David Lang
2006-08-04 18:38 ` Jeremy Fitzhardinge
2006-08-04 18:46 ` Antonio Vargas
2006-08-04 19:06 ` David Lang
2006-08-04 19:26 ` Arjan van de Ven
2006-08-04 19:45 ` David Lang
2006-08-04 20:11 ` Jeremy Fitzhardinge
2006-08-04 20:31 ` David Lang
2006-08-04 21:26 ` Jeremy Fitzhardinge
2006-08-04 21:40 ` Bill Rugolsky Jr.
2006-08-04 22:00 ` Arjan van de Ven
2006-08-04 22:45 ` David Lang
2006-08-04 19:45 ` Jeff Dike
2006-08-04 19:49 ` David Lang
2006-08-04 21:46 ` Jeff Dike
2006-08-04 22:40 ` David Lang
2006-08-04 5:40 ` Chris Wright
2006-08-04 6:28 ` Antonio Vargas [this message]
2006-08-04 7:01 ` Chris Wright
2006-08-04 7:19 ` Antonio Vargas
2006-08-04 7:37 ` Chris Wright
2006-08-04 18:34 ` Chris Wright
2006-08-04 20:41 ` Zachary Amsden
2006-08-04 20:52 ` Chris Wright
2006-08-04 21:26 ` Alan Cox
2006-08-05 1:14 ` James Bottomley
2006-08-05 5:37 ` Zachary Amsden
2006-08-05 10:42 ` Adrian Bunk
2006-08-05 11:50 ` Alan Cox
2006-08-04 22:01 ` Andi Kleen
2006-08-04 22:39 ` Zachary Amsden
2006-08-04 22:52 ` Andi Kleen
2006-08-04 22:43 ` David Lang
2006-08-05 10:47 ` Adrian Bunk
2006-08-05 11:57 ` Andi Kleen
2006-08-05 1:30 ` James Bottomley
2006-08-05 4:33 ` Zachary Amsden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=69304d110608032328r36bc0a6ase0a2dbf36d8cc519@mail.gmail.com \
--to=windenntw@gmail.com \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=greg@kroah.com \
--cc=hch@infradead.org \
--cc=ian.pratt@xensource.com \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.com \
--cc=jlo@vmware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=simon@xensource.com \
--cc=torvalds@osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®