From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wei Huang Subject: Re: RFC: Still TODO for 4.2? Date: Wed, 4 Jan 2012 13:21:46 -0600 Message-ID: <4F04A6CA.3010907@amd.com> References: <1325694562.25206.304.camel@zakaz.uk.xensource.com> <20120104172519.GS12984@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20120104172519.GS12984@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel , Keir Fraser , Ian Campbell , Tim Deegan , Ian Jackson , Stefano Stabellini , Jan Beulich List-Id: xen-devel@lists.xenproject.org On 01/04/2012 11:25 AM, Pasi K=E4rkk=E4inen wrote: > On Wed, Jan 04, 2012 at 04:29:22PM +0000, Ian Campbell wrote: >> What are the outstanding things to do before we think we can start on >> the 4.2 -rc's? Does anyone have a timetable in mind? >> >> hypervisor: >> >> * ??? - Keir, Tim, Jan? >> >> tools: >> >> * libxl stable API -- we would like 4.2 to define a stable API >> which downstream's can start to rely on not changing. Aspects of >> this are: >> * event handling (IanJ working on this) >> * drop libxl_device_model_info (move bits to build_info or >> elsewhere as appropriate) (IanC working on this, patches >> shortly) >> * add libxl_defbool and generally try and arrange that >> memset(foo,0,...) requests the defaults (IanC working on >> this, patches shortly) >> * The topologyinfo datastructure should be a list of >> tuples, not a tuple of lists. (nobody currently looking >> at this, not 100% sure this makes sense, could possibly >> defer and change after 4.2 in a compatible way) >> * Block script support -- can be done post 4.2? >> * Hotplug script stuff -- internal to libxl (I think, therefore I >> didn't put this under stable API above) but still good to have >> for 4.2? Roger Pau Monet was looking at this but its looking >> like a big can-o-worms... >> * Integrate qemu+seabios upstream into the build (Stefano has >> posted patches, I guess they need refreshing and reposting). No >> change in default qemu for 4.2. >> * More formally deprecate xm/xend. Manpage patches already in >> tree. Needs release noting and communication around -rc1 to >> remind people to test xl. >> >> Has anybody got anything else? I'm sure I've missed stuff. Are there any >> must haves e.g. in the paging/sharing spaces? >> > - What's the status of Nested Hardware Virtualization? > I remember some email saying Intel vmx-on-vmx has some performance issues, > and amd svm-on-svm works better.. > > > - Also there's a bunch of VGA passthru related patches, > that I once volunteered to collect/rebase/cleanup/repost myself, > but I still haven't had time for that :( Since there were quite a lot of interest on this subject, should we = document it in a separate wiki for working combinations (like = hypervisor, dom0, gfx card, driver version, tricks, etc)? > > -- Pasi > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >