From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.2 Release Plan / TODO Date: Thu, 22 Mar 2012 10:08:50 +0000 Message-ID: References: <1332154645.9223.35.camel@zakaz.uk.xensource.com> <1332409993.8817.44.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <1332409993.8817.44.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: xen-devel List-Id: xen-devel@lists.xenproject.org On Thu, Mar 22, 2012 at 9:53 AM, Ian Campbell wro= te: > On Thu, 2012-03-22 at 09:35 +0000, George Dunlap wrote: >> On Mon, Mar 19, 2012 at 10:57 AM, Ian Campbell = wrote: >> > =A0 =A0 =A0* xl compatibility with xm: >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* feature parity wrt driver domain support = (George Dunlap) >> I just discovered (while playing with driver domains) that xl is >> missing one bit of feature parity with xm for pci passthrough for PV >> guests -- and that's the "pci quirk" config file support. =A0I'm going >> to ask Intel if they have an interest in porting it over; I think it >> should at least be a "nice-to-have", and it may be a low-level >> blocker, as a lot of devices won't work passed through without it. > > This is the stuff in tools/python/xen/xend/server/pciquirk.py ? > > pciback in upstream doesn't mention "quirk" which suggests no support > for the necessary sysfs node either? Ah, interesting -- that's worth tracking down. Maybe there's a better way to deal with quirks? Or maybe it just hasn't been upstreamed yet (or perhaps even implemented in pvops?). I'm using the Debian squeeze 2.6.32-5-xen-686 kernel. > tools/examples/xend-pci-quirks.sxp =A0seems to only have a quirk for a > single card? Yes, well I could add two more cards just from experience w/ one of my test boxen. :-) > I don't think we want to implement an SXP parser for xl/libxl so if this > is reimplemented I think a different format should be used. Since we're using yajl anyway, JSON might not be a bad option. Anyway, I'll ping the Intel guy who recently posted a patch to libxl_pci.c. -George > > Anyway, I'll put this onto the list. > > Ian > >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* xl support for "rtc_timeoffset" and "loca= ltime" (Lin >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Ming, Patches posted) >> > =A0 =A0 =A0* More formally deprecate xm/xend. Manpage patches already = in >> > =A0 =A0 =A0 =A0tree. Needs release noting and communication around -rc= 1 to >> > =A0 =A0 =A0 =A0remind people to test xl. >> > =A0 =A0 =A0* Domain 0 block attach & general hotplug when using qdisk = backend >> > =A0 =A0 =A0 =A0(need to start qemu as necessary etc) (Stefano S) >> > =A0 =A0 =A0* file:// backend performance. qemu-xen-tradition's qdisk i= s quite >> > =A0 =A0 =A0 =A0slow & blktap2 not available in upstream kernels. Need = to >> > =A0 =A0 =A0 =A0consider our options: >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* qemu-xen's qdisk is thought to be well pe= rforming but >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0qemu-xen is not yet the default. Comple= xity arising from >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0splitting qemu-for-qdisk out from qemu-= for-dm and >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0running N qemu's. >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* potentially fully userspace blktap could = be ready for >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A04.2 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* use /dev/loop+blkback. This requires loop= driver AIO and >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0O_DIRECT patches which are not (AFAIK) = yet upstream. >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* Leverage XCP's blktap2 DKMS work. >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* Other ideas? >> > =A0 =A0 =A0* Improved Hotplug script support (Roger Pau Monn=E9, patch= es >> > =A0 =A0 =A0 =A0posted) >> > =A0 =A0 =A0* Block script support -- follows on from hotplug script (R= oger >> > =A0 =A0 =A0 =A0Pau Monn=E9) >> > >> > hypervisor, nice to have: >> > =A0 =A0 =A0* solid implementation of sharing/paging/mem-events (using = work >> > =A0 =A0 =A0 =A0queues) (Tim Deegan, Olaf Herring et al -- patches post= ed) >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* "The last patch to use a waitqueue in >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0__get_gfn_type_access() from Tim works.= =A0However, there >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0are a few users who call __get_gfn_type= _access with the >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0domain_lock held. This part needs to be= addressed in >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0some way." >> > =A0 =A0 =A0* Sharing support for AMD (Tim, Andres). >> > =A0 =A0 =A0* PoD performance improvements (George Dunlap) >> > >> > tools, nice to have: >> > =A0 =A0 =A0* Configure/control paging via xl/libxl (Olaf Herring, lots= of >> > =A0 =A0 =A0 =A0discussion around interface, general consensus reached = on what >> > =A0 =A0 =A0 =A0it should look like) >> > =A0 =A0 =A0* Upstream qemu feature patches: >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* Upstream qemu PCI passthrough support (An= thony Perard, >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0patches sent) >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* Upstream qemu save restore (Anthony Perar= d, Stefano >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Stabellini, patches sent, waiting for u= pstream ack) >> > =A0 =A0 =A0* Nested-virtualisation. Currently "experimental". Likely to >> > =A0 =A0 =A0 =A0release that way. >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* Nested SVM. Tested in a variety of config= urations but >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0still some issues with the most importa= nt use case (w7 >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0XP mode) [0] =A0(Christoph Egger) >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* Nested VMX. Needs nested EPT to be genuin= ely useful. >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Need more data on testedness etc (Intel) >> > =A0 =A0 =A0* Initial xl support for Remus (memory checkpoint, blackhol= ing) >> > =A0 =A0 =A0 =A0(Shriram, patches posted, blocked behind qemu save rest= ore >> > =A0 =A0 =A0 =A0patches) >> > =A0 =A0 =A0* xl compatibility with xm: >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* xl support for autospawning vncviewer (vn= cviewer=3D1 or >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0otherwise) (Goncalo Gomes) >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0* support for vif "rate" parameter (Mathieu= Gagn=E9) >> > >> > [0] http://lists.xen.org/archives/html/xen-devel/2012-03/msg00883.html >> > >> > >> > _______________________________________________ >> > Xen-devel mailing list >> > Xen-devel@lists.xen.org >> > http://lists.xen.org/xen-devel > >