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


Re: [Xen-devel] xen patches are in 2.6.37

To: Josip Rodin <joy@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen patches are in 2.6.37
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Sat, 30 Oct 2010 12:29:00 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 30 Oct 2010 12:31:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20101029181006.GA19688@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.LFD.2.00.1010290834430.16185@xxxxxxxxxxxxxxx> <20101029094641.GL2804@xxxxxxxxxxx> <4CCAFB35.6030505@xxxxxxxx> <20101029181006.GA19688@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20100921 Fedora/3.1.4-1.fc13 Lightning/1.0b3pre Thunderbird/3.1.4
 On 10/29/2010 11:10 AM, Josip Rodin wrote:
> Are you going to make a temporary branch where you'll just slap on the
> missing code (even the non-upstreamable parts), just so we can test the full
> Xen dom0 stack in the current circumstances? Upstream kernel has undergone
> many changes since .32 and it stands to reason that there are other bugs to
> flush out, unrelated to code upstreamability.

Yes, I want to keep a full-featured Xen kernel tracking upstream
releases.  But I'd like to put a strong emphasis on making sure that
components which must be upstreamed (ie, to get a useful system), or are
very close to upstreamable should be kept in an upstreamable form.

In general, stuff that I think is plausible for upstream, or actually
being upstreamed, will be in upstream/*.   Those branches are also
highly dynamic (rebasing, etc), so never use them as the base for your
own branches...


Xen-devel mailing list