From: Gerd Hoffmann <kraxel@suse.de>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH,RFC 0/17] 32-on-64 work progress
Date: Wed, 11 Oct 2006 12:16:36 +0200 [thread overview]
Message-ID: <452CC484.6060403@suse.de> (raw)
In-Reply-To: <C1527AC6.255C%Keir.Fraser@cl.cam.ac.uk>
Keir Fraser wrote:
> On 11/10/06 10:11, "Gerd Hoffmann" <kraxel@suse.de> 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 <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-10-11 10:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 15:26 [PATCH,RFC 0/17] 32-on-64 work progress Jan Beulich
2006-10-05 9:41 ` Gerd Hoffmann
2006-10-05 12:49 ` Jan Beulich
2006-10-11 9:11 ` Gerd Hoffmann
2006-10-11 9:41 ` Keir Fraser
2006-10-11 10:16 ` Gerd Hoffmann [this message]
2006-10-11 10:20 ` Keir Fraser
-- strict thread matches above, loose matches on Subject: below --
2006-10-14 9:56 Jan Beulich
2006-10-16 8:39 ` Gerd Hoffmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=452CC484.6060403@suse.de \
--to=kraxel@suse.de \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.