All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@suse.de>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH,RFC 0/17] 32-on-64 work progress
Date: Wed, 11 Oct 2006 11:11:25 +0200	[thread overview]
Message-ID: <452CB53D.60603@suse.de> (raw)
In-Reply-To: <45251B96.76E4.0078.0@novell.com>

  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 <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg

  reply	other threads:[~2006-10-11  9:11 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 [this message]
2006-10-11  9:41       ` Keir Fraser
2006-10-11 10:16         ` Gerd Hoffmann
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=452CB53D.60603@suse.de \
    --to=kraxel@suse.de \
    --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.