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. Thanks! / magnus _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Muli Ben-Yehuda
2006-Apr-04 05:29 UTC
Re: [Xen-devel] separate components and broken out patches
On Tue, Apr 04, 2006 at 12:09:53PM +0900, Magnus Damm wrote:> 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 > - toolsJust a heads up, in case you aren''t aware of it, there''s an hg kernel tree that''s cloned from the upstream kernel that you can use to work on the kernel in the comfort of ... an hg tree. I use it for all of my Xe kernel work and it''s infinitely better (for me) than the sparse/patches combination. The tree is at http://xenbits.xensource.com/linux-2.6-xen.hg. Cheers, Muli -- Muli Ben-Yehuda http://www.mulix.org | http://mulix.livejournal.com/ _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Magnus Damm
2006-Apr-04 06:50 UTC
Re: [Xen-devel] separate components and broken out patches
On 4/4/06, Muli Ben-Yehuda <mulix@mulix.org> wrote:> On Tue, Apr 04, 2006 at 12:09:53PM +0900, Magnus Damm wrote: > > > 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 > > Just a heads up, in case you aren''t aware of it, there''s an hg kernel > tree that''s cloned from the upstream kernel that you can use to work > on the kernel in the comfort of ... an hg tree. I use it for all of my > Xe kernel work and it''s infinitely better (for me) than the > sparse/patches combination. The tree is at > http://xenbits.xensource.com/linux-2.6-xen.hg.Oh, excellent! That''s much nicer IMO. Thanks for pointing that out! / magnus _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel