WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] Structure of the Xen source code

To: "Pradeep Singh, TLS-Chennai" <pradeep_s@xxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] Structure of the Xen source code
From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Date: Tue, 20 Feb 2007 11:08:55 +0100
Delivery-date: Tue, 20 Feb 2007 02:08:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <66E8AEE9980BB44CA5FCAD39EBA56AC67EDF3F@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcdUMrLZPBqRLQ4JTBKoxnklKEMAywAAHHlQABr3orwAAHVVigANSV/g
Thread-topic: [Xen-devel] Structure of the Xen source code
> Depends on what you want to achieve... Understanding ALL of 
> Xen is a LOT
> of effort. Understanding enough to be able to do what you 
> need to do may
> be a lot less. What is the target of your "studying the code"?
> 
> Target to understand how exactly Xen is booted and initialized.

Boot consists of:
Grub loads and decompresses Xen.gz + Linux-kernel [+ optional ramdisk +
optional security features]

It then jumps to the entry-point in xen.gz, which will do some
initialization before it jumps to the entry point of the Linux kernel
(Dom0 or "host"). 

> On second thought this is what i understood from my study.
> Xen binary sits with the patched xen dom0 kernel above hardware.
> Am i right?

Yes, that's pretty much it. 
> 
> When we say Xen binary i.e the first line of the Xen entry in 
> Grub(e.g xen.gz), this is different from the patched dom0 
> kernel, right?

Yes, those are two different binaries, with different purposes. Xen.gz
is the hypervisor, the linux kernel is a (modified) Linux operating
system kernel. The hypervisor is used by all guests (in this case Dom0
is also considered a guest, it's just a "special" guest). 

> 
> I look at this as
> 
> xen.gz -> hypervisor
Yes. 
> linux.2.6.x.-xen.dom0 -> patched host kernel
Yes. 
> linux.2.6.x-xen.domU -> patched/unpatched guest kernel we 
> want to boot.
If it's an "unpatched kernel" then it's not supplied in the source-code
of Xen. Unpatced kernels come from the guest-OS install CD (or similar).


As Daniel Stodden explained, there are also tools and other directorys
with "parts of Xen", including a documentation directory. 

--
Mats

> 
> Please CMIIW.
> 
> TIA
> Pradeep
> 
> >
> > If a doc about code organisation of the Xen can be given that
> > will be great.
> >
> > Any other links or pointer'll be appreciated.
> >
> > Thanks in Advance
> >
> > pradeep
> >
> >
> >
> >
> >
> >
> >
> 
> 
> 
> 
> 
> 
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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