From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Re: Features scheduled for the 2.6.39 merge window
Date: Fri, 11 Mar 2011 09:24:21 -0500 [thread overview]
Message-ID: <20110311142421.GB4880@dumpdata.com> (raw)
In-Reply-To: <288478695.20110311123403@eikelenboom.it>
On Fri, Mar 11, 2011 at 12:34:03PM +0100, Sander Eikelenboom wrote:
> Hello Ian,
>
> Friday, March 11, 2011, 12:03:39 PM, you wrote:
>
> > On Fri, 2011-03-11 at 10:57 +0000, Sander Eikelenboom wrote:
> >> Hi All,
> >>
> >> I have lost a bit of track on what (backend) features are scheduled for the 2.6.39 merge window.
>
> > Konrad posted a state of the world for this last night, see the thread
> > "2.6.39 merge window (git pulls and what is planned to go in)"
>
> >> Of special interest for me:
>
> > I'm afraid you are rather out of luck in that respect :-(
>
> >> - blkback (tapdisk2?)
>
> > Not planned for 2.6.39.
>
> >> - netback
>
> > Under review on the netdev list, might still make it.
>
> >> - pciback
>
> > Not planned for 2.6.39.
>
> > FWIW blkback, netback and pciback all have relatively clean branches
> > which could be pulled in for testing purposes though.
>
> Hmmm looking at Konrad's git tree, the master tree seems to be just that in this case :-)
> Will try it later this weekend.
Yeah, except that it does not work right now with legacy IRQ (like USB devices)
passthrough - just found out about that yesterday when I started running it through the paces.
But it works fine for PV, HVM, and Dom 0 case.
next prev parent reply other threads:[~2011-03-11 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 10:57 Features scheduled for the 2.6.39 merge window Sander Eikelenboom
2011-03-11 11:03 ` Ian Campbell
2011-03-11 11:12 ` Sander Eikelenboom
2011-03-11 11:34 ` Sander Eikelenboom
2011-03-11 14:24 ` Konrad Rzeszutek Wilk [this message]
2011-03-11 17:06 ` Sander Eikelenboom
2011-03-11 19:49 ` Sander Eikelenboom
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=20110311142421.GB4880@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=linux@eikelenboom.it \
--cc=xen-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.