All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: "Daniel P. Smith" <dpsmith@apertussolutions.com>
Cc: christopher.w.clark@gmail.com, andrew.cooper3@citrix.com,
	stefano.stabellini@xilinx.com, jgrall@amazon.com,
	Julien.grall.oss@gmail.com, iwj@xenproject.org, wl@xen.org,
	george.dunlap@citrix.com, persaur@gmail.com,
	Bertrand.Marquis@arm.com, roger.pau@citrix.com,
	luca.fancellu@arm.com, paul@xen.org, adam.schwalm@starlab.io,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH 0/2] Introducing hyperlaunch capability design (formerly: DomB mode of dom0less)
Date: Tue, 30 Mar 2021 16:31:21 +0200	[thread overview]
Message-ID: <bd61f993-f719-ec87-638f-f53d6e983c3e@suse.com> (raw)
In-Reply-To: <6314f50f-b4fc-e472-4c9a-3591e168d2c3@apertussolutions.com>

On 16.03.2021 04:56, Daniel P. Smith wrote:
> To assist in reading, please find attached rendered copies of the design
> docs. It should be noted that due to poor rendering by pandoc, we forced
> the tables to stay as ASCII tables in the patches whereas the attached
> docs have the tables rendered properly by rst2pdf.

In section 3.6 I found "As a result, on x86 the hyperlaunch capability does
not rely on nor preclude any specific BIOS boot protocol, i.e legacy BIOS
boot or UEFI boot. The only requirement is that the boot loader supports
the Multiboot2 (MB2) protocol." I'm afraid the two sentences contradict
one another, as UEFI on its own doesn't provide MB2 functionality. It is
my understanding that you don't require this anyway - what you need is a
way to load modules beyond just Dom0 kernel and an initrd.

I'm also struggling to see how you mean to associate the (MB2) modules
passed to Xen with the individual functions. I.e. I don't see how it will
be ensure that the embedded mb-index is in sync with the order or modules
actually supplied.

As to modules - iirc there are placement restrictions by at least some
boot loaders (below 4Gb). If that's correct, do you have any thoughts
towards dealing with the limited space available to hold these modules?
I've seem systems with lots of memory, but with as little as just 1Gb
below the 4Gb boundary.

Jan


  reply	other threads:[~2021-03-30 14:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16  3:18 [PATCH 0/2] Introducing hyperlaunch capability design (formerly: DomB mode of dom0less) Daniel P. Smith
2021-03-16  3:18 ` [PATCH 1/2] docs/designs/launch: hyperlaunch design document Daniel P. Smith
2021-03-18 16:43   ` Roger Pau Monné
2021-03-23 17:39     ` Christopher Clark
2021-03-24  8:01       ` Roger Pau Monné
2021-03-24 12:53         ` Christopher Clark
2021-03-24 13:15           ` George Dunlap
2021-03-24 19:10           ` Stefano Stabellini
2021-03-25  8:07             ` Jan Beulich
2021-03-25  8:32           ` Roger Pau Monné
2021-03-25  9:14             ` George Dunlap
2021-03-25  9:49               ` Roger Pau Monné
2021-03-25 16:55                 ` Stefano Stabellini
2021-04-07 20:14                   ` Christopher Clark
2021-03-16  3:18 ` [PATCH] docs/designs/launch: hyperlaunch device tree Daniel P. Smith
2021-03-16  3:56 ` [PATCH 0/2] Introducing hyperlaunch capability design (formerly: DomB mode of dom0less) Daniel P. Smith
2021-03-30 14:31   ` Jan Beulich [this message]
2021-04-07 19:23     ` Christopher Clark
2021-04-08  5:56       ` Jan Beulich
2021-04-15 22:33         ` Christopher Clark

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=bd61f993-f719-ec87-638f-f53d6e983c3e@suse.com \
    --to=jbeulich@suse.com \
    --cc=Bertrand.Marquis@arm.com \
    --cc=Julien.grall.oss@gmail.com \
    --cc=adam.schwalm@starlab.io \
    --cc=andrew.cooper3@citrix.com \
    --cc=christopher.w.clark@gmail.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=george.dunlap@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=jgrall@amazon.com \
    --cc=luca.fancellu@arm.com \
    --cc=paul@xen.org \
    --cc=persaur@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=stefano.stabellini@xilinx.com \
    --cc=wl@xen.org \
    --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.