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 16:29:57 +0000 Message-ID: <50F82705.1000909@eu.citrix.com> References: <50F7CDBF02000078000B6A95@nat28.tlf.novell.com> <50F7DCA2.1070405@eu.citrix.com> <50F801F102000078000B6CEE@nat28.tlf.novell.com> <50F80378.4070105@eu.citrix.com> <50F815AC02000078000B6DC2@nat28.tlf.novell.com> <50F80B95.3010005@eu.citrix.com> <50F8270902000078000B6E48@nat28.tlf.novell.com> <50F81D33.9030200@eu.citrix.com> <50F8318C02000078000B6ED6@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: <50F8318C02000078000B6ED6@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: Konrad Rzeszutek Wilk , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On 17/01/13 16:14, Jan Beulich wrote: >> Therefore, if we want Ubuntu+Xen to have the same functionality as >> Ubuntu w/o Xen, then: >> * When the dom0 kernel is signed, Xen will need to leave boot-time >> services enabled > Once again - this is a no-go. All boot services memory got > reclaimed by the time Dom0 gets launched, so there's no way > for Dom0 to access boot services. Even Xen itself cannot > arbitrarily use them - they get turned of near the end of > efi_start(). Anything else is conceptually wrong, even if it > might be possible to be made work. Right -- well "this is probably impossible" is different than, "you shouldn't need to". :-) >> So unless we plan to handle the same quirks in Xen, we're going to need >> to make it possible for dom0 to do it. > We will have to - see my other reply. I suppose then we'll have to plan on it. In that case, it would be good if, sometime in the next month or two, someone could take a look at exactly what these "quirks" are that Linux needs boot services for, and figure out whether we are likely to need them. I'll put that in a sort of "call to action", along with any other important features not currently on track to make it into 4.3. -George