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-users] Re: [Xen-devel] Linux 2.6.39 - what Xen components went

To: Sander Eikelenboom <linux@xxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Re: [Xen-devel] Linux 2.6.39 - what Xen components went in.
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sun, 15 May 2011 18:51:27 +0300
Cc: Joseph Glanville <joseph.glanville@xxxxxxxxxxxxxx>, Jeremy Fitzhardinge <jeremy@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Sun, 15 May 2011 08:52:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <13910110377.20110514093443@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: <20110513143615.GA16193@xxxxxxxxxxxx> <BANLkTim_hgQ2qPWr9aZ8OtTrurz4LqA=jw@xxxxxxxxxxxxxx> <20110513164927.GA18484@xxxxxxxxxxxx> <13910110377.20110514093443@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, May 14, 2011 at 09:34:43AM +0200, Sander Eikelenboom wrote:
> Friday, May 13, 2011, 6:49:27 PM, you wrote:
> > On Sat, May 14, 2011 at 12:46:18AM +1000, Joseph Glanville wrote:
> >> Great work everyone. :)
> > Combined with this week acceptance of Xen in upstream QEMU, and I think
> > that the majority of folks on xen-devel are going to have a hard hangover
> > on Monday :-)
> Cheers and thx all ! :-)
> >> 
> >> I assume this means that drivers/block/xen-blkback.c is the last major
> >> milestone to be pushed upstream?
> > There are also some semi-major ones, but right now the xen-blkback is 
> > important
> > since it provides so much more performance benefit than the QEMU one.
> A semi one for me personally would be acpi-processor stuff to make xenpm work.
> But having blkback would make it at least ok to test for some longer period 
> :-)

At Xen Hack-a-tron two months ago Jeremy was mentioning pvops acpi patches..

Jeremy: Any plans for submitting those upstream? 

-- Pasi

Xen-devel mailing list