From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Mark Langsdorf" <mark.langsdorf@calxeda.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Fabien Chouteau" <chouteau@adacore.com>,
"Alexander Graf" <agraf@suse.de>,
"Blue Swirl" <blauwirbel@gmail.com>,
"Michael Walle" <michael@walle.cc>,
"Hervé Poussineau" <hpoussin@reactos.org>,
"Paul Brook" <paul@codesourcery.com>,
"Anthony Liguori" <anthony@codemonkey.ws>,
qemu-ppc <qemu-ppc@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] turn firmware image filename into a machine option
Date: Wed, 02 Oct 2013 00:23:29 +1000 [thread overview]
Message-ID: <524ADAE1.2030802@ozlabs.ru> (raw)
In-Reply-To: <524AD24C.1020709@suse.de>
On 10/01/2013 11:46 PM, Andreas Färber wrote:
> Am 01.10.2013 15:41, schrieb Gerd Hoffmann:
>> On Di, 2013-10-01 at 14:20 +0200, Andreas Färber wrote:
>>> Hi,
>>>
>>> Am 01.10.2013 14:16, schrieb Gerd Hoffmann:
>>>>> -bios we're stuck with because it's a legacy
>>>>> option,
>>>>
>>>> What is legacy about it?
>>>>
>>>> Well, the x86-centric name of course. Thats why the machine option is
>>>> named 'firmware' instead.
>>>>
>>>> It also doesn't use QemuOpts, which is fixed by this patch.
>>>>
>>>> Anything else?
>>>
>>> The basic assumption that there is only one piece of firmware. Just like
>>> -bios, -machine firmware= will allow only one entry. sPAPR has two.
>>
>> --verbose please. What they are needed for?
>
> SLOF and RTAS. SLOF is the firmware, and RTAS is requested by the OS
> through OpenFirmware client interface.
>
> It is not device-specific, it is more or less part of the firmware but
> copied to RAM. I'll let Alex or Alexey comment in more details.
SLOF is what is loaded from the very beginning, it configures PCI, cooks
the device tree and boots the guest system (directly or via yaboot/grub,
from disk, network or ram). Normal firmware, as usual. It knows all the
details about the machine so the guest system (linux) does not need to know
details about PCI host bus adapter or anything like this.
RTAS is an agent which always lives in RAM when the guest system (linux,
aix) is up and running. It is a light-weight version of SLOF which is left
in RAM by SLOF and can do board/machine specific tasks such as PCI config
space access or PCI hotplug - something what SLOF already knows about and
something what the guest does not want to know about in details. This came
from IBM pHyp (traditional server PPC64 hypervisor) and it is quite a big
firmware. In the case of KVM, it is very small stub which simply passes
requests to QEMU which does the rest. But it is still a separate binary
image even in the current QEMU.
May be some day it will become bigger as from time to time the community
wants things to be done in a certain way which would mean extending rtas,
however we (powerpc-server folks) want to hope it won't happen ever :)
Adding Ben in copy, he might have something to add.
--
Alexey
next prev parent reply other threads:[~2013-10-01 14:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 9:39 [Qemu-devel] [PATCH] turn firmware image filename into a machine option Gerd Hoffmann
2013-10-01 10:55 ` Peter Maydell
2013-10-01 11:22 ` Gerd Hoffmann
2013-10-01 11:32 ` Peter Maydell
2013-10-01 12:16 ` Gerd Hoffmann
2013-10-01 12:20 ` Andreas Färber
2013-10-01 13:41 ` Gerd Hoffmann
2013-10-01 13:46 ` Andreas Färber
2013-10-01 14:23 ` Alexey Kardashevskiy [this message]
2013-10-01 14:40 ` Gerd Hoffmann
2013-10-01 14:45 ` Alexander Graf
2013-10-01 21:23 ` Benjamin Herrenschmidt
2013-10-02 1:18 ` Alexey Kardashevskiy
2013-10-01 13:00 ` Peter Maydell
2013-10-01 14:57 ` Paolo Bonzini
2013-10-01 15:05 ` Gerd Hoffmann
2013-10-01 15:12 ` Peter Maydell
2013-10-01 15:28 ` Paolo Bonzini
2013-10-01 15:42 ` Anthony Liguori
[not found] ` <524AB29F.3030906@suse.de>
2013-10-01 13:32 ` Gerd Hoffmann
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=524ADAE1.2030802@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=chouteau@adacore.com \
--cc=hpoussin@reactos.org \
--cc=kraxel@redhat.com \
--cc=mark.langsdorf@calxeda.com \
--cc=michael@walle.cc \
--cc=paul@codesourcery.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).