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? More general question - can anyone venture an estimate on when all remaining dom0 features will be merged into Linus tree ? Regards, RW _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, 2011-02-24 at 10:41 +0000, 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?No. rc6 is way to late to be expecting new features to go into Linux.> More general question - can anyone venture an estimate on when all remaining dom0 > features will be merged into Linus tree ?I can only speak for netback which I am targeting at the 2.6.39 merge window. It''s had a couple of rounds of review on linux-netdev already and I think it is getting to be in ok shape so I''m hopeful. I believe Konrad has a pciback branch but I don''t know what timescale he is looking at for merging. If there is anything else you are keen to see go in then volunteering to clean it up and work with upstream to get it reviewed and merged would be the most effective way to ensure it happens. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 :-) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Feb 24, 2011 at 7:53 AM, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> wrote:> 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 :-)With 2-3 month release cycles, 2.6.42 is by end of this year? Now, thats looong way :-) shriram> > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel