From: Tim Deegan <Tim.Deegan@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: lei yang <yanglei.fage@gmail.com>,
George Dunlap <dunlapg@umich.edu>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Xen, List <xen-users@lists.xensource.com>
Subject: Re: [Xen-devel] Re: How to build a 64 bit xen
Date: Tue, 18 May 2010 16:30:01 +0100 [thread overview]
Message-ID: <20100518153001.GI4164@whitby.uk.xensource.com> (raw)
In-Reply-To: <1274196015.6180.243.camel@zakaz.uk.xensource.com>
At 16:20 +0100 on 18 May (1274199615), Ian Campbell wrote:
> On Tue, 2010-05-18 at 16:13 +0100, George Dunlap wrote:
> > I've cross-compiled 64-bit xen exclusively since I've worked for
> > XenSource basically. Here's what I get:
> >
> > $ file xen/xen
> > xen/xen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
> > statically linked, stripped
> > $ file xen/xen-syms
> > xen/xen-syms: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
> > statically linked, not stripped
> >
> > So I think 'file' is just making a mistake.
>
> The 64 bit hypervisor really is encapsulated in a 32 bit container, see
> the mkelf32 related rules in xen/arch/x86/Makefile.
>
> I'm not sure why. Something to do with 32 bit bootloaders maybe?
Yep. The Multiboot standard specifies that the kernel should be started
in 32-bit protected mode with flat 4GB segments. Xen bootstraps itself
from there up into 64-bit mode.
Tim.
--
Tim Deegan <Tim.Deegan@citrix.com>
Principal Software Engineer, XenServer Engineering
Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
next prev parent reply other threads:[~2010-05-18 15:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 13:11 How to build a 64 bit xen lei yang
2010-05-18 14:40 ` lei yang
2010-05-18 15:13 ` George Dunlap
2010-05-18 15:20 ` Ian Campbell
2010-05-18 15:25 ` [Xen-devel] " Keir Fraser
2010-05-18 15:26 ` lei yang
2010-05-18 15:30 ` Tim Deegan [this message]
2010-06-01 16:07 ` Mike Viau
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=20100518153001.GI4164@whitby.uk.xensource.com \
--to=tim.deegan@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=dunlapg@umich.edu \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
--cc=yanglei.fage@gmail.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.