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: Mon, 16 Oct 2006 10:39:31 +0200 Message-ID: <45334543.9040106@suse.de> References: <4530C25A0200007800024383@emea5-mh.id5.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4530C25A0200007800024383@emea5-mh.id5.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, > I didn't spend thoughts on the tools side - Emmanuel was expected to > work from that side I think. surely what you say needs to be considered > (and for the part of those hypercalls already implemented should already be, > minus any bugs or oversights) How do they work? Using the native version of dom0 (as suggested by Keir) for those hypercalls where it is possible? How do you handle setvcpucontest, where the 64bit struct isn't a superset of the 32bit version? I think for at least that one, maybe also others, we have to pass compat structs through native hypercalls. And maybe also visa versa, so you can boot 64bit guests when running 32bit dom0 (within some limits of course ...). My current stack of patches (which also includes some other bits) is here: http://www.suse.de/~kraxel/patches/kraxel-unstable-zweiblum-hg11751-quilt/ Alot of the domain builder code can handle non-native guests already, the hypercalls which actually boot the domain are still missing though. cheers, Gerd -- Gerd Hoffmann http://www.suse.de/~kraxel/julika-dora.jpeg