Understood.
--- On Sun, 4/12/09, Boris Derzhavets <bderzhavets@xxxxxxxxx> wrote:
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Christophe Saout" <christophe@xxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Sunday, April 12, 2009, 2:57 PM
What branch to check
out ?
Boris
--- On Sun, 4/12/09, Christophe Saout <christophe@xxxxxxxx> wrote:
From: Christophe Saout <christophe@xxxxxxxx>
Subject: Re: [Xen-devel] Re: NX related build failure in latest pv_ops dom0 hackery tree
To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Sunday, April 12, 2009, 12:55 PM
Hi Pasi,
> > Latest tree (as of today) doesn't seem to build for me:
> > [...]
> >
> > Known problem?
>
> [written by Jeremy Fitzhardine:]
>
> Yes, sorry. I haven't been updating hackery much lately during the
> merge window. When we see what actually got merged next week,
I'll be
> rebuilding the xen.git branch structure into something a bit cleaner to
> go on with.
I think push2/xen/dom0/master is in a workable state.
In the meantime, you can try to use that tree:
http://git.saout.de/gitweb/?p=linux-dom0-pvops.git;a=summary
It's the latest tip.git merged with one of the push branches from
Jeremy's git repo and cherry-picked commits from the backend, blkback
and netback trees plus minor merge conflict and compile problem fixups.
It seems feature-complete to me, stable and is able to run DomU domains
without problems.
Christophe
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
