From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [PATCH,RFC 0/17] 32-on-64 work progress Date: Wed, 11 Oct 2006 12:16:36 +0200 Message-ID: <452CC484.6060403@suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Jan Beulich List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 11/10/06 10:11, "Gerd Hoffmann" wrote: > >> Do you have any plans how domU bootup is going to work? Especially how >> hypercalls where one domain (typically dom0) changes the state of >> another domain are supposed to work? That includes the complete >> XEN_DOMCTL_* family, also some memory management hypercalls such as >> mach2phys and pagetable updates, maybe more. These are used by the >> domain tools to create a new domain and somehow must handle the case >> that we want be able to build 32bit guest domains from a 64bit dom0 (and >> visa versa?). > > The tools are going to have to know that they are building a 32p-on-64 > guest. What problems do you perceive? Sure, they have to know. Question is what do you pass in when changing a 32bit guest from 64bit dom0. The 32bit struct? The 64bit struct? I think in many cases both will work just fine and we have just have to pick one way. XEN_DOMCTL_setvcpucontext is a icky one though, the 64bit struct isn't a superset of the 32bit struct, so we probably have to pass the 32bit version for 32bit guests. cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg