From: Paolo Bonzini <pbonzini@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Thomas Huth <thuth@redhat.com>,
Alexey Kardashevskiy <aik@ozlabs.ru>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Cornelia Huck <conny@cornelia-huck.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Stefano Garzarella <sgarzare@redhat.com>
Subject: Re: VW ELF loader
Date: Thu, 6 Feb 2020 09:29:07 +0100 [thread overview]
Message-ID: <73105e0b-c0a0-009f-aeba-fec818d3088c@redhat.com> (raw)
In-Reply-To: <20200205055851.GH60221@umbus.fritz.box>
On 05/02/20 06:58, David Gibson wrote:
>> Yes, SLOF is big and slow. petitboot is not petit at all either, and
>> has the disadvantage that you have to find a way to run GRUB afterwards.
> Well, not usually. Petitboot parses grub configuration itself, which
> means that generally from the OS / installer point of view it looks
> like grub, even though it's not from the actual bootstrapping point of
> view.
Ok, sorry about that. I need to learn a bit more.
>> But would a similarly minimal OF implementation (no network, almost no
>> interpret so no Forth, device tree built entirely in the host, etc.) be
>> just as big and slow?
>
> So, as actual OF implementations go, SLOF is already pretty minimal
> (hence "Slim Line Open Firmware"). If there's no Forth, it's really
> not OF any more, just something mimicing some of OF's interfaces.
Right, not unlike what you get with vof=on. :) I'm not against at all
that idea. I just don't understand what you refer to below as (2).
Does petitboot not have the problem because it kexecs the new kernel?
Paolo
> But the difficulty of SLOF isn't really its bigness or slowness in any
> case (the slowness is just an additional irritation). The two big
> issues are 1) that it's written in an obscure language and 2)
> synchronizing its state with things that require host side
> involvement.
>
> Rewriting a minimal guest side not-OF would partly address (1) (but
> there's still the logistical pain of having to build and insert it),
> and wouldn't address (2) at all.
next prev parent reply other threads:[~2020-02-06 8:30 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-01 13:39 VW ELF loader Alexey Kardashevskiy
2020-02-01 19:04 ` Paolo Bonzini
2020-02-02 11:51 ` Alexey Kardashevskiy
2020-02-02 17:38 ` Paolo Bonzini
2020-02-03 1:31 ` David Gibson
2020-02-03 1:28 ` David Gibson
2020-02-03 9:12 ` Paolo Bonzini
2020-02-03 9:50 ` David Gibson
2020-02-03 10:58 ` Alexey Kardashevskiy
2020-02-03 15:08 ` Paolo Bonzini
2020-02-03 22:36 ` Alexey Kardashevskiy
2020-02-03 22:56 ` Paolo Bonzini
2020-02-03 23:19 ` Alexey Kardashevskiy
2020-02-03 23:26 ` Paolo Bonzini
2020-02-04 6:16 ` Thomas Huth
2020-02-04 8:54 ` Cornelia Huck
2020-02-04 9:20 ` Restrictions of libnet (was: Re: VW ELF loader) Thomas Huth
2020-02-04 9:32 ` Thomas Huth
2020-02-04 9:33 ` Michal Suchánek
2020-02-05 5:30 ` David Gibson
2020-02-05 6:24 ` Thomas Huth
2020-02-10 7:55 ` David Gibson
2020-02-10 9:39 ` Michal Suchánek
2020-02-13 3:16 ` David Gibson
2020-02-04 23:18 ` VW ELF loader Alexey Kardashevskiy
2020-02-05 6:06 ` David Gibson
2020-02-05 9:28 ` Cornelia Huck
2020-02-06 4:47 ` David Gibson
2020-02-06 8:27 ` Paolo Bonzini
2020-02-06 23:17 ` Alexey Kardashevskiy
2020-02-06 23:45 ` Paolo Bonzini
2020-02-10 7:30 ` David Gibson
2020-02-10 10:37 ` Peter Maydell
2020-02-10 11:25 ` Paolo Bonzini
2020-02-14 3:23 ` David Gibson
2020-02-10 7:28 ` David Gibson
2020-02-10 11:26 ` Paolo Bonzini
2020-02-14 4:02 ` David Gibson
2020-02-05 5:58 ` David Gibson
2020-02-06 8:29 ` Paolo Bonzini [this message]
2020-02-06 23:23 ` Alexey Kardashevskiy
2020-02-06 23:46 ` Paolo Bonzini
2020-02-10 0:31 ` Alexey Kardashevskiy
2020-02-13 1:43 ` Alexey Kardashevskiy
2020-02-13 10:17 ` Paolo Bonzini
2020-02-14 0:01 ` Alexey Kardashevskiy
2020-02-14 2:30 ` David Gibson
2020-02-04 9:40 ` Christian Borntraeger
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=73105e0b-c0a0-009f-aeba-fec818d3088c@redhat.com \
--to=pbonzini@redhat.com \
--cc=aik@ozlabs.ru \
--cc=borntraeger@de.ibm.com \
--cc=conny@cornelia-huck.de \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=thuth@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).