All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Daniel Kiper <daniel.kiper@oracle.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH RFC 6/7] xen/x86/efi: Verify dom0 kernel with SHIM_LOCK protocol in efi_multiboot2()
Date: Tue, 15 May 2018 02:06:52 -0600	[thread overview]
Message-ID: <5AFA951C02000078001C2C0C@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <20180514165653.GP12135@olila.local.net-space.pl>

>>> On 14.05.18 at 18:56, <daniel.kiper@oracle.com> wrote:
> On Mon, May 14, 2018 at 04:43:13AM -0600, Jan Beulich wrote:
>> >>> On 08.05.18 at 15:09, <daniel.kiper@oracle.com> wrote:
>> > On Fri, May 04, 2018 at 09:46:33AM -0600, Jan Beulich wrote:
>> >> >>> On 08.07.17 at 23:53, <daniel.kiper@oracle.com> wrote:
>> >> > @@ -484,9 +497,12 @@ __efi64_mb2_start:
>> >> >          /* Keep the stack aligned. Do not pop a single item off it. */
>> >> >          mov     (%rsp),%rdi
>> >> >
>> >> > +        mov     %r14d,%edx
>> >> > +
>> >> >          /*
>> >> >           * efi_multiboot2() is called according to System V AMD64 ABI:
>> >> > -         *   - IN:  %rdi - EFI ImageHandle, %rsi - EFI SystemTable.
>> >> > +         *   - IN: %rdi - EFI ImageHandle, %rsi - EFI SystemTable,
>> >> > +         *         %rdx - dom0 kernel module struct address.
>> >>
>> >> How come everything further up treats this as a 32-bit quantity only?
>> >
>> > According to the Multiboot2 spec the bootloader is not allowed to
>> > put the kernel (xen.gz) and the modules above 4 GiB boundary.
>>
>> Interesting - how would they load a 1Gb initrd on a system with just 1Gb
>> RAM below 4Gb? Not to speak of a 4Gb initrd ...
> 
> That is not possible right now. This requires changes in the boot protocol.
> Anyway, have you seen such setups in the wild today?

Years ago we've already had to make our XenoLinux forward port cope with
512Mb+ initrd-s - see the commit introducing XEN_ELFNOTE_MOD_START_PFN,
which tells you that Xen itself needed to be changed for this as well. Those
folks wanted to be able to boot a full fledged distro without loading anything
from disk (or network) post-boot.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-15  8:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-08 21:53 [PATCH RFC 0/7] Change xen.efi build and add SHIM_LOCK verification into efi_multiboot2() Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 1/7] xen: Introduce XEN_COMPILE_POSIX_TIME Daniel Kiper
2018-04-30 15:56   ` Jan Beulich
2018-05-08 12:18     ` Daniel Kiper
2018-05-14 10:30       ` Jan Beulich
2018-05-14 16:25         ` Daniel Kiper
2018-05-15  7:47           ` Jan Beulich
2017-07-08 21:53 ` [PATCH RFC 2/7] xen/x86: Manually build PE header Daniel Kiper
2018-05-04 15:38   ` Jan Beulich
2018-05-08 12:47     ` Daniel Kiper
2018-05-14 10:40       ` Jan Beulich
2018-05-14 16:52         ` Daniel Kiper
2018-05-15  8:01           ` Jan Beulich
2017-07-08 21:53 ` [PATCH RFC 3/7] xen/x86: Add some addresses to the Multiboot header Daniel Kiper
2018-05-04 15:40   ` Jan Beulich
2018-05-08 13:01     ` Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 4/7] xen/x86: Add some addresses to the Multiboot2 header Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 5/7] efi: split out efi_shim_lock() Daniel Kiper
2017-07-08 21:53 ` [PATCH RFC 6/7] xen/x86/efi: Verify dom0 kernel with SHIM_LOCK protocol in efi_multiboot2() Daniel Kiper
2018-05-04 15:46   ` Jan Beulich
2018-05-08 13:09     ` Daniel Kiper
2018-05-14 10:43       ` Jan Beulich
2018-05-14 16:56         ` Daniel Kiper
2018-05-15  8:06           ` Jan Beulich [this message]
2017-07-08 21:53 ` [PATCH RFC 7/7] xen/x86: Build xen.mb.efi directly from xen-syms Daniel Kiper

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=5AFA951C02000078001C2C0C@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=xen-devel@lists.xenproject.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.