All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Gorm Hansen <jacobg@diku.dk>
To: Tobias Hunger <tobias@aquazul.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Xen as a kernel module
Date: Fri, 28 Jan 2005 12:09:42 -0800	[thread overview]
Message-ID: <41FA9C06.8000506@diku.dk> (raw)
In-Reply-To: <200501271605.19343.tobias@aquazul.com>

Tobias Hunger wrote:
> 
>>Right now Xen is mapped somewhere in top of memory, I am not sure how
>>domains are kept out of there, but I suppose it has to do with segments.
> 
> 
> As I understand this xen runs in ring0 and pushes the guests kernels one ring 
> up into ring1 and then uses traps to allow the guest OSes to trap into the 
> hypervisor as necessary.
> 
> 
>>The good thing about that is that hypercalls are cheap, and in Xen1.x
>>I/O was cheap as well.
> 
> 
> Cheap where? In dom0 or the VMs?

Both. Assuming that context switching is an expensive operation, and 
that most of the cost comes from flushing the TLBs, the current model 
has more overhead than a model where the drivers are mapped into the 
same address space (though still protected from domU access other that 
through hypercalls) as the currently running domain. Xen already 
contains magic that allows it to be permanently mapped into running 
domains, while still being protected from accidential/malicious access.

I am calling that monolithic, because that is what standard linux does, 
and what the old Xen 1.x did. The current model is more like a 
microkernel, such as L4 or Mach (though of course a lot more clever, no 
offense people ;-))

Apart from perhaps increasing performance, I was saying it would be cool 
if the Xen-interface could be provided on platforms such as Windows or 
native Linux. People have done similar stuff before (e.g. VMWare vmmon, 
the Adeos nanokernel, coLinux), so it should be possible. It seems Xen 
would have better chances of world domination that way, if that is a 
goal. It would also save some duplication of effort in porting guestOSes 
to the different models out there.

Anyway, it was just an idea, and it is likely that with future hardware 
the Xen NGIO/microkernel model will finally be overhead-free, vendors 
will start writing Xen-VM drivers, and we will all live happily ever 
after :-).

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

  parent reply	other threads:[~2005-01-28 20:09 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
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 [this message]
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=41FA9C06.8000506@diku.dk \
    --to=jacobg@diku.dk \
    --cc=tobias@aquazul.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.