From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>,
Arnd Bergmann <arnd@arndb.de>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mathiasen@gmail.com, virtualization@lists.linux-foundation.org
Subject: Re: A set of "standard" virtual devices?
Date: Tue, 03 Apr 2007 13:03:15 -0700 [thread overview]
Message-ID: <4612B303.5000109@zytor.com> (raw)
In-Reply-To: <4612B123.2040105@goop.org>
Jeremy Fitzhardinge wrote:
>
> Yes, and that's the core of the Xen netfront. But is there really much
> code which can be shared between different hypervisors? When you get
> down to it, all the real code is hypervisor-specific stuff for setting
> up ringbuffers and dealing with interrupts. Like all the other network
> drivers.
>
One thing, Jeremy, which I think is being a bit misleading here: you're
focusing on big, performance-critical stuff. Those things are going to
be the ones which has the most win to implement in hypervisor-specific
ways. Although we can offer models for some hypervisors (and G-d knows
there are enough implementations out there of virtual disk which are
almost identical), they're clearly not going to be universal.
However, there are other things; console is some, or my original
example, which was random number generation. For those, the benefit of
unification is proportionally greater, simply because the win of
anything hypervisor-specific is much smaller.
-hpa
WARNING: multiple messages have this Message-ID (diff)
From: "H. Peter Anvin" <hpa@zytor.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Cornelia Huck <cornelia.huck@de.ibm.com>, Andi Kleen <ak@suse.de>,
Christian Borntraeger <borntrae@de.ibm.com>,
virtualization@lists.linux-foundation.org,
Virtualization Mailing List <virtualization@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
mathiasen@gmail.com
Subject: Re: A set of "standard" virtual devices?
Date: Tue, 03 Apr 2007 13:03:15 -0700 [thread overview]
Message-ID: <4612B303.5000109@zytor.com> (raw)
In-Reply-To: <4612B123.2040105@goop.org>
Jeremy Fitzhardinge wrote:
>
> Yes, and that's the core of the Xen netfront. But is there really much
> code which can be shared between different hypervisors? When you get
> down to it, all the real code is hypervisor-specific stuff for setting
> up ringbuffers and dealing with interrupts. Like all the other network
> drivers.
>
One thing, Jeremy, which I think is being a bit misleading here: you're
focusing on big, performance-critical stuff. Those things are going to
be the ones which has the most win to implement in hypervisor-specific
ways. Although we can offer models for some hypervisors (and G-d knows
there are enough implementations out there of virtual disk which are
almost identical), they're clearly not going to be universal.
However, there are other things; console is some, or my original
example, which was random number generation. For those, the benefit of
unification is proportionally greater, simply because the win of
anything hypervisor-specific is much smaller.
-hpa
next prev parent reply other threads:[~2007-04-03 20:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 20:18 A set of "standard" virtual devices? H. Peter Anvin
2007-04-02 20:31 ` Roland Dreier
2007-04-02 20:33 ` H. Peter Anvin
2007-04-02 21:49 ` Roland Dreier
2007-04-02 20:56 ` Jeremy Fitzhardinge
2007-04-02 21:12 ` Andi Kleen
2007-04-02 21:33 ` Jeff Garzik
2007-04-02 21:33 ` Jeff Garzik
2007-04-02 21:36 ` Andi Kleen
2007-04-02 21:36 ` Andi Kleen
2007-04-02 21:42 ` Jeremy Fitzhardinge
2007-04-02 21:42 ` Jeremy Fitzhardinge
2007-04-02 21:53 ` Anthony Liguori
2007-04-02 21:53 ` Anthony Liguori
2007-04-02 22:04 ` Jeremy Fitzhardinge
2007-04-02 22:10 ` H. Peter Anvin
2007-04-02 22:10 ` H. Peter Anvin
2007-04-02 22:25 ` Jeff Garzik
2007-04-02 22:25 ` Jeff Garzik
2007-04-02 22:30 ` H. Peter Anvin
2007-04-02 22:30 ` H. Peter Anvin
2007-04-03 9:41 ` Arnd Bergmann
2007-04-03 10:41 ` Cornelia Huck
2007-04-03 12:15 ` Arnd Bergmann
2007-04-03 13:39 ` Cornelia Huck
2007-04-03 14:03 ` Arnd Bergmann
2007-04-03 16:07 ` Cornelia Huck
2007-04-03 8:29 ` Christian Borntraeger
2007-04-03 8:30 ` Andi Kleen
2007-04-03 9:17 ` Cornelia Huck
2007-04-03 9:26 ` Andi Kleen
2007-04-03 10:51 ` Cornelia Huck
2007-04-03 15:00 ` Adrian Bunk
2007-04-03 17:50 ` Arnd Bergmann
2007-04-03 17:50 ` Arnd Bergmann
2007-04-03 19:07 ` Jeremy Fitzhardinge
2007-04-03 19:42 ` Arnd Bergmann
2007-04-03 19:55 ` Jeremy Fitzhardinge
2007-04-03 20:03 ` H. Peter Anvin [this message]
2007-04-03 20:03 ` H. Peter Anvin
2007-04-03 21:00 ` Jeremy Fitzhardinge
2007-04-03 21:00 ` Jeremy Fitzhardinge
2007-04-03 21:45 ` H. Peter Anvin
2007-04-03 21:51 ` Arnd Bergmann
2007-04-03 22:10 ` H. Peter Anvin
2007-04-03 22:10 ` H. Peter Anvin
2007-04-03 22:49 ` Arnd Bergmann
2007-04-04 0:52 ` H. Peter Anvin
2007-04-04 13:11 ` Arnd Bergmann
2007-04-04 15:50 ` H. Peter Anvin
2007-04-03 20:50 ` Arnd Bergmann
2007-04-03 20:50 ` Arnd Bergmann
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=4612B303.5000109@zytor.com \
--to=hpa@zytor.com \
--cc=arnd@arndb.de \
--cc=cornelia.huck@de.ibm.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathiasen@gmail.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=virtualization@lists.osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.