All of lore.kernel.org
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: xen-devel@lists.xen.org
Subject: Re: [PATCH v2 00/23] x86: multiboot2 protocol support
Date: Fri, 30 Oct 2015 08:44:53 -0700	[thread overview]
Message-ID: <56339075.9010403@gmail.com> (raw)

Re:

	> The final goal is xen.efi binary file which could be loaded by EFI
	> loader, multiboot (v1) protocol (only on legacy BIOS platforms) and
	> multiboot2 protocol. This way we will have:
	>   - smaller Xen code base,
	>   - one code base for xen.gz and xen.efi,
	>   - one build method for xen.gz and xen.efi;
	>     xen.efi will be extracted from xen file
	>     using objcopy; PE header will be contained
	>     in ELF file and will precede Xen code,
	>   - xen.efi build will not so strongly depend
	>     on a given GCC and binutils version.


As of v220, systemd provides systemd-boot (formerly gummiboot)

     https://wiki.archlinux.org/index.php/Boot_loaders#systemd-boot
     https://wiki.archlinux.org/index.php/Systemd-boot#EFI_boot

and is apparently capable of booting EFISTUB kernels.

Will the aforementioned goals enable direct boot using systemd-boot on 
EFI platforms ?  Or is it possible even now?

As my current test distro is Opensuse, with systemd v < 220, I've not 
yet tested.

             reply	other threads:[~2015-10-30 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-30 15:44 PGNet Dev [this message]
2015-10-30 17:29 ` [PATCH v2 00/23] x86: multiboot2 protocol support Daniel Kiper
2015-10-30 18:06   ` PGNet Dev
2015-10-30 18:23     ` Daniel Kiper
2015-10-30 18:36       ` PGNet Dev
2015-10-30 20:04         ` Daniel Kiper
  -- strict thread matches above, loose matches on Subject: below --
2015-07-20 14:28 Daniel Kiper
2015-07-20 14:28 Daniel Kiper
2015-07-21  9:39 ` Jan Beulich
2015-07-21  9:39 ` Jan Beulich

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=56339075.9010403@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=xen-devel@lists.xen.org \
    /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.