From mboxrd@z Thu Jan 1 00:00:00 1970 From: George Dunlap Subject: Re: Xen 4.3 development update, and stock-taking Date: Thu, 17 Jan 2013 11:12:34 +0000 Message-ID: <50F7DCA2.1070405@eu.citrix.com> References: <50F7CDBF02000078000B6A95@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <50F7CDBF02000078000B6A95@nat28.tlf.novell.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: Jan Beulich Cc: Matthew Fioravante , Ian Campbell , Wei Liu , Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" , Jim Fehlig , Anthony Perard , Daniel De Graaf , Roger Pau Monne List-Id: xen-devel@lists.xenproject.org On 17/01/13 09:09, Jan Beulich wrote: >>>> On 16.01.13 at 18:55, George Dunlap wrote: >> * Persistent grants for blk (external) >> owner: roger.pau@citrix >> status: Initial implementation posted >> prognosis: ? > I think this went into 3.8-rc. Ah, great. > >> * Scalability: 16TiB of RAM >> owner: jan@suse >> status: Not started > Patches almost ready to be posted (working fine for "normal" > mode, but working on simulating the mode we'd be in when > having this much of memory). > > Prognosis: Good. Good, I'll update that. > >> * Remove hardcoded mobprobe's in xencommons >> owner: ? >> status: ? >> prognosis: Poor. > This was actually _promised_ to be a temporary hack, so I'd > consider it a release blocker if nothing at all was done here. I agree. But I thought it would be useful *first* to have a clear list of where everything is. Then when we know what's at-risk, we can decide which things are critical / blockers and have a call to action. > >> * Xen EFI boot >> - Signature checking for dom0 kernel / initrd? >> status: No owner. >> prognosis: Probably not for 4.4 > This is already in the tree (c/s 26262:b62bd62b2683). Nothing else > should be necessary on the hypervisor side if the shim is to be used. > > But of course pv-ops Linux continues to lack EFI support altogether. OK, so I think the description needs an update, then. For Xen to be fully featured, I think it would need all of the following: * An EFI-bootable dom0 (this should be done, right?) * dom0 able to make use of EFI run-time services * Xen able to use EFI boot-time services (?) * Xen able to detect the existence of a signed Linux binary, and leave EFI boot-time services enabled for dom0 to use when appropriate * dom0 able to use boot-time EFI services and disable them when done Are any of these that should be blockers for 4.3? -George