All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Zhuan Chen <zhuanchen@gmail.com>, xen-devel@lists.xen.org
Subject: Re: Building 32-bit xen.efi for 32-bit EFI platforms
Date: Mon, 24 Nov 2014 15:09:39 +0000	[thread overview]
Message-ID: <54734A33.6040600@citrix.com> (raw)
In-Reply-To: <CAGG8cjVOoYjBmmjjBUHVxjO0autOWE_GoHamuaC+=6rQVBs5kQ@mail.gmail.com>

On 24/11/14 14:59, Zhuan Chen wrote:
> Hi,
>
> I am wondering whether it's possible to build 32-bit xen.efi for the
> 32-bit EFI platform? One way of building xen.efi I learnt is to make
> the binutils configured with the x86_64-pep emulation (according to
> the document http://xenbits.xenproject.org/docs/unstable/misc/efi.html).
> The resulted xen.efi is 64-bit mode. Is it possible to build xen.efi
> as the 32-bit mode?
>
> The reason for this question is due to my effort of installing Xen on
> the Asus Transformer Book T100, which is one of the Bay Trail Atom
> (64-bit processors) tablets shipped with 32-bit EFI firmware. This
> requires the support of the 32-bit EFI bootloader. Such platforms seem
> to become common and Linux kernel from 3.15 also provides the EFI
> mixed mode to support 64-bit kernels running from 32-bit EFI firmware.
>
> Thanks,
> Zhuan

32bit Xen support was removed in Xen 4.3, so building a pure 32bit
hypervisor is not possible.

There is an argument to be made for building a 32bit Xen.efi which is
bootable by a 32bit firmware and moves into 64bit mode on boot.

There is however no support for this that I am aware of.

~Andrew

  reply	other threads:[~2014-11-24 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 14:59 Building 32-bit xen.efi for 32-bit EFI platforms Zhuan Chen
2014-11-24 15:09 ` Andrew Cooper [this message]
2014-11-24 15:22   ` Ian Campbell
2014-11-24 16:16 ` Jan Beulich
2014-12-01 13:11 ` David Vrabel

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=54734A33.6040600@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zhuanchen@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.