[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH RFC 0/5] Split off mini-os to a separate tree



On 30 January 2015 at 11:26, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
> On Mon, Jan 26, 2015 at 09:53:25AM +0000, Thomas Leonard wrote:
>> [ Cc += Anil ]
>>
>> On 25 January 2015 at 18:25, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
>> > Cc Ian and Ian and some folks who might be interested in this work.
>> >
>> > On Sun, Jan 25, 2015 at 06:13:41PM +0000, Wei Liu wrote:
>> >> There has been increasing use of mini-os in unikernel world and basically
>> >> everybody has their own fork of mini-os. That way going foward is going
>> >> to cause fragmentation of the community.
>> >>
>> >> We would like to split off mini-os tree so that everybody can upstream 
>> >> their
>> >> changes and work on a common code base. Later I would also like to setup
>> >> a proper push gate for mini-os.
>> >>
>> >> Stubdom's build environment is known to be very fragile, so basically all 
>> >> the
>> >> real work is done in top level Makefile.
>> >>
>> >> I use following runes to split off mini-os:
>> >>
>> >>   git filter-branch --tag-name-filter cat \
>> >>     --subdirectory-filter extras/mini-os/ -- --all
>> >>
>> >>   # There is already a tag name 4.3.0-rc2 which points to the same commit.
>> >>   git tag -d xen-4.3.0-rc2
>> >>
>> >>   # Add xen- prefix to all tags
>> >>   for t in `git tag`; do git tag "xen-$t" "$t"; git tag -d "$t" ; done
>> >>
>> >>   git gc --aggressive
>> >>
>> >> The tree can be found at:
>> >>   git://xenbits.xen.org/people/liuw/mini-os.git master
>> >>
>> >> Note that mini-os cannot build on its own due to the limitation of it's 
>> >> own
>> >> build system. Splitting it off it's the first step towards fixing that 
>> >> problem
>>
>> In case it's useful: for the standalone version of Mini-OS used by
>> Mirage, I had to include these directories too:
>>
>> 1. xen/include/public
>> 2. xen/common/libfdt
>> 3. xen/include/xen/libfdt
>
> Is libfdt required? I see inclusion of libfdt.h in arch/arm/mm.c but I
> couldn't find trace to link libfdt in Makefile. And I ran a simple test
> to compile minios in Xen tree on an arm board it doesn't compile.
>
> If arm support is still WIP I'm going to ignore libfdt for now.

The ARM port works fine, but you need to apply the last couple of
patches in the series (the rest are already in). The latest versions
are on my "next" branch here:

  https://github.com/talex5/xen/commits/next

If you want to test it, you need these two:

- mini-os: arm: interrupt controller
- mini-os: arm: build system

> Wei.
>
>> 4. config
>>
>> ( https://github.com/talex5/xen/tree/minios-releases )
>>
>> Will there be a separate mailing list for Mini-OS? That would be very
>> useful for people who don't want to keep up with xen-devel.
>>
>> Thanks!
>>
>>
>> --
>> Dr Thomas Leonard        http://0install.net/
>> GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
>> GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA



-- 
Dr Thomas Leonard        http://0install.net/
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.