From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Joseph Glanville <joseph.glanville@orionvm.com.au>,
Jeremy Fitzhardinge <jeremy@goop.org>,
xen-devel@lists.xensource.com, xen-users@lists.xensource.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xen-users] Re: Linux 2.6.39 - what Xen components went in.
Date: Sun, 15 May 2011 18:51:27 +0300 [thread overview]
Message-ID: <20110515155127.GL32595@reaktio.net> (raw)
In-Reply-To: <13910110377.20110514093443@eikelenboom.it>
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
next prev parent reply other threads:[~2011-05-15 15:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 14:36 Linux 2.6.39 - what Xen components went in Konrad Rzeszutek Wilk
2011-05-13 14:46 ` [Xen-devel] " Joseph Glanville
2011-05-13 16:49 ` Konrad Rzeszutek Wilk
2011-05-14 7:34 ` [Xen-devel] " Sander Eikelenboom
2011-05-15 15:51 ` Pasi Kärkkäinen [this message]
2011-05-16 16:27 ` [Xen-users] " Jeremy Fitzhardinge
2011-05-16 16:49 ` Re: [Xen-devel] " Konrad Rzeszutek Wilk
2011-05-16 20:45 ` [Xen-users] " Sander Eikelenboom
2011-05-14 9:32 ` [Xen-devel] " Thomas Goirand
2011-05-14 15:02 ` Konrad Rzeszutek Wilk
2011-05-15 4:32 ` Thomas Goirand
2011-05-15 13:10 ` Pasi Kärkkäinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110515155127.GL32595@reaktio.net \
--to=pasik@iki.fi \
--cc=jeremy@goop.org \
--cc=joseph.glanville@orionvm.com.au \
--cc=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).