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] separate components and broken out patches

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] separate components and broken out patches
From: "Magnus Damm" <magnus.damm@xxxxxxxxx>
Date: Tue, 4 Apr 2006 12:09:53 +0900
Delivery-date: Mon, 03 Apr 2006 20:10:14 -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:content-transfer-encoding:content-disposition; b=DX8gw2JIJyIBbqr6Cr5OxapS6DZ8w6I6qoj9LA2KDNuxdZRcQ9//Hvx+/DENvL8MDQgHP18VtI1m3E8b7pn7MDlpYQ9KSB3iGLrHd1sc39w2sN4AvTjTO+8PC0JDccnBf0GtGJ/2aNJEE1SaM9H0+2JTWB8UYRlnWb3NaD99LbY=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
Hi all,

I've been playing with the hg xen-unstable tree for a while now, and
after poking around in the source tree a bit I think I've figured out
how the build system is working.

I am a bit surprised by the mix of sparse and patches, and I find that
combination quite hard to work with. I'm mostly interested in the
kernel part of xen for now, and for that kind of work I prefer broken
out patches.

So to make my kernel work easier I've hacked on breaking out code from
the xen-unstable tree into three separate components:

- kernel
- hypervisor
- tools

Each of these components are stand alone but some header files are
"shared", ie present in each component. I've managed to create base
tarballs (or a base patch for the vanilla kernel) and broken out
patches on top of the base files. The broken out patches are generated
from hg using some magic shell scripts.

The components above build ok, and I find it good that the kernel and
hypervisor could easily be cross compiled compared to the tools that
require a more complex cross tool environment.

If anyone is interested in extending this idea or merging patches let me know.


/ magnus

Xen-devel mailing list

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