From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Timeline for migrating to newer Linux kernels?
Date: Mon, 01 Jan 2007 17:20:03 -0800
Message-ID: <4599B343.2060908@goop.org>
References: <BD262A443AD428499D90AF8368C4528D1C2D9D@fmsmsx411.amr.corp.intel.com>
	<45985425.6010307@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45985425.6010307@redhat.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Rik van Riel <riel@redhat.com>
Cc: "Zulauf, John" <john.zulauf@intel.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Rik van Riel wrote:
> If XenSource has any intention of having Xen stay relevant
> in the future, they'll want to seriously pursue an upstream
> merge of their code.

That's an active project.  The paravirt ops patches have been laying the
groundwork, and I'm planning on posting the Xen patches based on it in
the next few days when I get back from vacation.  Once Xen is in the
kernel, the parallel project will be to make the hg Xen tree sync with
it.  There will still need to be some external patches, but they will
diminish over time.

    J