From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Rafal Wojtczuk <rafal@invisiblethingslab.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: dom0 features in Linus tree
Date: Thu, 24 Feb 2011 10:53:00 -0500 [thread overview]
Message-ID: <20110224155300.GC6893@dumpdata.com> (raw)
In-Reply-To: <20110224104114.GB2221@email>
On Thu, Feb 24, 2011 at 11:41:14AM +0100, Rafal Wojtczuk wrote:
> Hello,
>
> I have just noticed that vanilla linux-2.6.38-rc6 does not have pciback, nor
> netback. Does anyone know whether these two will be included in final 2.6.38?
I was thinking 2.6.39, but then I was also wondering whether some of this
functionality it provides can be exposed via QEMU PCI API and KVM's interrupt
handler code (similar to pciback, except that the flow is via ioctl/eventfs
to/from QEMU for PCI devices interrupts). It would require delicate surgery
in multiple code bases but could make it easier in the long-term.
Still pondering about it, but in the meantime there is a branch that works
quite nicely
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git devel/next-2.6.38
and has netback+pciback and is quite stable on my boxes.
>
> More general question - can anyone venture an estimate on when all remaining dom0
> features will be merged into Linus tree ?
To give ourselves a lot of breathing room for fixing bugs, stabilizing, etc, testing,
how about 2.6.42?
The more I see the number 42 the better that answer is :-)
next prev parent reply other threads:[~2011-02-24 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 10:41 dom0 features in Linus tree Rafal Wojtczuk
2011-02-24 11:08 ` Ian Campbell
2011-02-24 15:53 ` Konrad Rzeszutek Wilk [this message]
2011-02-24 23:44 ` Shriram Rajagopalan
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=20110224155300.GC6893@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=rafal@invisiblethingslab.com \
--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.