[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] context switch and hypervisor


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Chris Zhang" <abnamro.chris@xxxxxxxxx>
  • Date: Fri, 15 Sep 2006 16:11:15 +1000
  • Delivery-date: Thu, 14 Sep 2006 23:11:46 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=BNcVQYsKO15VkUyhFpxYX8DZFEHAjtf0pN7A7gF/HQ/ouSLsUaQGEsOLlXDeLiTIKrOMChRck6S3EPrX4vaTZPEr8BHeqwiRfqjTE9KxbFnG8LZOV5rAgsD2BI2ST9cZ02nis40+E2xPoMdMjUgmRzS7cZfcCuiXArZ86coNrHQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi,
 
I have been reading some papers from Xen and other sources, there are just a couple of questions that I found hard to understand.
 
Why is Xen hypervisor better than a traditional hypervisor? With a traditional hypervisor, during a context switch, the hypervisor stores the states of a guest OS then goes to the next OS, upon coming back to the first OS it restores the hardware states then passes it on to the first OS. Does Xen pretty much do the same thing except it provides an API to the OS, and the reason/benefit of having such an API is to reduce the time for a TLB flush?
 
Can someone please explain this to me in detail?
 
Cheers
 
Chris
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.