This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Hypervisor architecture?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Hypervisor architecture?
From: Etienne Martineau <etmartin@xxxxxxxxx>
Date: Tue, 04 May 2010 12:25:07 -0700
Authentication-results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
Delivery-date: Tue, 04 May 2010 12:27:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Is there any documents around that describe the 'internal' architecture
of the Hypervisor?

So far my understanding is such that the Hypervisor is a 'strip-down'
Linux 2.6.(12/13) + lot's of customization specific to Xen. 

Because there is so much documentation around for the Linux kernel I
think it would be _nice_ to have a 'conceptual mapping' between the
Hypervisor and the Linux kernel....

For example:
-Under Linux, processes are described by 'struct task_struct'
-Under Hypervisor, VMs are described by 'struct domain'

What is common?
What is different?

For those who are already familiar with the Linux kernel there would be
a net advantage when trying to 'pickup' on how things are done within
the hypervisor


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>