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 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest
Date: Wed, 23 Aug 2006 13:44:06 +0200 [thread overview]
Message-ID: <44EC3F86.9000409@suse.de> (raw)
In-Reply-To: <C111EE4C.1456%Keir.Fraser@cl.cam.ac.uk>
Hi,
> If we do 32-bit dom0 kernel then the tools will pick up the 32-bit version
> of that structure. So this is only an issue for userspace if we want 64-bit
> dom0 to be able to build 32-bit domU's. I suppose this would be nice to
> have.
I think we certainly want to have that. I'd suggest to have a look at
my kexec bits:
http://www.suse.de/~kraxel/xen/kexec.html
http://www.suse.de/~kraxel/patches/
They include a largely rewritten domain builder, adding support for
loading both 32bit and 64bit kernels with the 64bit tools should be easy.
> Obvious thing to do is suffix all the structs and defns in arch-x86_foo.h
> with _32 or _64 as appropriate. Then, at the end of the header, we define
> the non-suffixed versions only if defined(__i386__) or __defined__(x86_64)
> (as appropriate).
I'd suggest to suffix them with $arch instead, so we have the option to
handle even ia64 on x86 machines.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-08-23 11:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 9:16 [PATCH 6/7, RFC] x86_64: basic changes for supporting compatibility mode guest Jan Beulich
2006-08-23 9:40 ` Keir Fraser
2006-08-23 10:17 ` Jan Beulich
2006-08-23 10:36 ` Keir Fraser
2006-08-23 11:10 ` Jan Beulich
2006-08-23 11:44 ` Gerd Hoffmann [this message]
2006-08-23 10:32 ` Jan Beulich
2006-08-23 10:33 ` 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=44EC3F86.9000409@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.