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 11:11:25 +0200 Message-ID: <452CB53D.60603@suse.de> References: <4523EEB2.76E4.0078.0@novell.com> <4524D34D.1050508@suse.de> <45251B96.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <45251B96.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi, >>> In an attempt to get some feedback on the ways I'm currently implementing >>> this, I'm sending the set of patches as I currently have them. These permit >>> a 32-bit PAE Linux dom0 kernel to come up on a 64-bit hypervisor, but >>> progress only goes this far currently (very early during invocation of the >>> first user mode code page table permissions aren't set correctly yet, making >>> Xen kill the guest). 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?). cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg