From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Kip Macy <kmacy@fsmware.com>
Cc: Xen-devel@lists.sourceforge.net
Subject: Re: Xen as a kernel module
Date: Tue, 25 Jan 2005 17:59:52 -0800 [thread overview]
Message-ID: <41F6F998.9010501@diku.dk> (raw)
In-Reply-To: <20050125173106.H89060@demos.bsdclusters.com>
Kip Macy wrote:
> I'm obviously partisan, but I think that would largely defeat the
> privilege de-coupling that they're trying to achieve. Not to mention
> nullifying the notion of a driver domain.
Is anyone actually using driver domains, other than dom0? It would be
really cool if hardware vendors started shipping drivers in Xen-VM
format, but until that happens I do not see much motivation for having
multiple full Linuxes around just to achieve a limited amount of isolation.
It is no secret that I much preferred the old and simpler model, but I
understand that noone likes having to port drivers, and I guess this is
one reason for the current state of things. With Xen inside the host OS
kernel, you would get the performance of the old model, and the ease of
development of the new model, plus potentially the option of running Xen
on millions of Windows-desktops (I am sure the Silicon Valley VCs would
love to hear that ;-)).
With all the OSes currently ported to Xen, the Xen hypercall interface
could become a de-facto standard for paravirtualized OSes, especially if
Xen were able to run on top of Windows as well as on top of Linux.
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-01-26 1:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 1:24 Xen as a kernel module Jacob Gorm Hansen
2005-01-26 1:32 ` Kip Macy
2005-01-26 1:59 ` Jacob Gorm Hansen [this message]
2005-01-26 4:30 ` Ronald G. Minnich
2005-01-26 8:41 ` Steven Hand
2005-01-26 23:19 ` Jacob Gorm Hansen
2005-01-27 15:05 ` Tobias Hunger
2005-01-28 18:32 ` Mark Williamson
2005-01-28 20:09 ` Jacob Gorm Hansen
2005-01-27 13:30 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2005-01-26 2:34 Neugebauer, Rolf
2005-01-26 3:12 ` Jacob Gorm Hansen
2005-01-26 7:55 ` Keir Fraser
2005-01-27 13:24 ` Mark Williamson
2005-01-28 20:59 ` Ronald G. Minnich
2005-01-28 23:16 ` Jacob Gorm Hansen
2005-01-28 23:26 ` Ronald G. Minnich
2005-01-28 23:29 ` Jacob Gorm Hansen
2005-01-29 2:15 ` Adam Sulmicki
2005-01-26 3:57 ` Ronald G. Minnich
2005-01-26 11:41 Ian Pratt
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=41F6F998.9010501@diku.dk \
--to=jacobg@diku.dk \
--cc=Xen-devel@lists.sourceforge.net \
--cc=kmacy@fsmware.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 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.