From: Andrea Bolognani <abologna@redhat.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
qemu-devel@nongnu.org
Cc: "Jose Ricardo Ziviani" <joserz@linux.ibm.com>,
"Fabiano Rosas" <farosas@linux.ibm.com>,
"Sam Bobroff" <sbobroff@linux.ibm.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Paul Mackerras" <paulus@ozlabs.org>,
qemu-ppc@nongnu.org,
"Leonardo Augusto Guimarães Garcia" <lagarcia@br.ibm.com>,
"Leonardo Bras" <leonardo@linux.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [RFC PATCH qemu] spapr: Kill SLOF
Date: Tue, 07 Jan 2020 10:39:21 +0100 [thread overview]
Message-ID: <e3299f0688127627de96eb2db1f127bf94df9085.camel@redhat.com> (raw)
In-Reply-To: <81f1f752-3ada-2c8d-38b7-1344c7633e14@ozlabs.ru>
On Tue, 2020-01-07 at 12:55 +1100, Alexey Kardashevskiy wrote:
> On 07/01/2020 01:15, Daniel Henrique Barboza wrote:
> > Question: does Petitboot already replaces SLOF in every possible
> > scenario for all
> > the spapr machine features?
>
> Petitboot kernel+initramdisk almost replaces SLOF + GRUB.
Is this necessarily a good thing? Personally I quite like the fact
that I can use the same bootloader across x86, ppc64 and aarch64.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2020-01-07 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 7:44 [RFC PATCH qemu] spapr: Kill SLOF Alexey Kardashevskiy
2020-01-05 23:38 ` Alexey Kardashevskiy
2020-01-06 14:15 ` Daniel Henrique Barboza
2020-01-07 1:55 ` Alexey Kardashevskiy
2020-01-07 9:39 ` Andrea Bolognani [this message]
2020-01-07 11:23 ` Thomas Huth
2020-01-14 9:04 ` Michal Suchánek
2020-01-08 2:34 ` Alexey Kardashevskiy
2020-01-13 9:13 ` Andrea Bolognani
2020-01-14 0:43 ` Alexey Kardashevskiy
2020-01-14 0:48 ` David Gibson
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=e3299f0688127627de96eb2db1f127bf94df9085.camel@redhat.com \
--to=abologna@redhat.com \
--cc=aik@ozlabs.ru \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=farosas@linux.ibm.com \
--cc=joserz@linux.ibm.com \
--cc=lagarcia@br.ibm.com \
--cc=leonardo@linux.ibm.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=paulus@ozlabs.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbobroff@linux.ibm.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).