From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: upstream merge status for 2.6.35, .36?
Date: Fri, 04 Jun 2010 17:20:06 -0700
Message-ID: <4C099836.1050903@goop.org>
References: <20100604223929.GA8819@orion.carnet.hr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <20100604223929.GA8819@orion.carnet.hr>
List-Unsubscribe: <http://lists.xensource.com/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/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: Josip Rodin <joy@entuzijast.net>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 06/04/2010 03:39 PM, Josip Rodin wrote:
> What about the future? I saw Konrad's applied his swiotlb tree with the
> right acks for inclusion into linux-next, so that looks like it's planned
> to be ready to go in when the .36 merge window opens, right?
>   

Yes, and I'm hoping we can get pcifront and pvhvm lined up for .36; with
those in place, its a short jump to full dom0 functionality (which, no
promises, might also get into .36 on their tails).

Then the backend drivers will be the next hurdle.  Plain blkback is
probably fairly straightforward, and netback can probably got
upsteamable with a small amount of effort.  But blktap2 and netchannel2
are pretty questionable at this point.  ACPI power management will also
need another round of attention.

    J