From: Daniel Henrique Barboza <danielhb413@gmail.com>
To: Alexey Kardashevskiy <aik@ozlabs.ru>, 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: Mon, 6 Jan 2020 11:15:57 -0300 [thread overview]
Message-ID: <dd98618f-01c6-850f-ac00-454a2f798508@gmail.com> (raw)
In-Reply-To: <3cf3e733-199a-61ba-7aaa-05e9546cd4d9@ozlabs.ru>
Hey,
On 1/5/20 8:38 PM, Alexey Kardashevskiy wrote:
> Another version is coming, I'll start putting fewer people in the cc:
> list, watch qemu-ppc@nongnu.org for further updates if interested. Thanks,
Question: does Petitboot already replaces SLOF in every possible scenario for all
the spapr machine features? Or is Petitboot 'good enough' to get the ball
rolling and then we'll incrementally improve Petitboot/spapr code to add the
missing bits?
I am asking because this "SLOF-less" feature is something we'll want to expose on
Libvirt - users will sure enjoy enjoy the shorter boot time - and I want to brace
for impact when users starts opening bugs about the SLOF-less machine missing stuff
that the SLOF version does.
Thanks,
DHB
next prev parent reply other threads:[~2020-01-06 14:17 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 [this message]
2020-01-07 1:55 ` Alexey Kardashevskiy
2020-01-07 9:39 ` Andrea Bolognani
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=dd98618f-01c6-850f-ac00-454a2f798508@gmail.com \
--to=danielhb413@gmail.com \
--cc=aik@ozlabs.ru \
--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).