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: Mon, 16 Oct 2006 10:39:31 +0200	[thread overview]
Message-ID: <45334543.9040106@suse.de> (raw)
In-Reply-To: <4530C25A0200007800024383@emea5-mh.id5.novell.com>

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

  reply	other threads:[~2006-10-16  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  9:56 [PATCH,RFC 0/17] 32-on-64 work progress Jan Beulich
2006-10-16  8:39 ` Gerd Hoffmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-04 15:26 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
2006-10-11 10:20           ` Keir Fraser

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=45334543.9040106@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.