From mboxrd@z Thu Jan  1 00:00:00 1970
From: Etienne Martineau <etmartin@cisco.com>
Subject: Hypervisor architecture?
Date: Tue, 04 May 2010 12:25:07 -0700
Message-ID: <1273001107.27500.5.camel@etienne-desktop>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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

-Etienne