motorhead/qemu
1
0
Fork 0
mirror of https://github.com/Motorhead1991/qemu.git synced 2025-07-28 21:03:54 -06:00
Code Issues Projects Releases Packages Wiki Activity Actions

docs: Clarifications and formatting changes in ppc docs.

Browse source 
Signed-off-by: Leonardo Garcia <lagarcia@br.ibm.com>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Message-Id: <3b228af4785241c7fb4a2c70f0c495d2a9adea83.1641405872.git.lagarcia@br.ibm.com>
Signed-off-by: Cédric Le Goater <clg@kaod.org>
This commit is contained in:
Leonardo Garcia 2022-01-12 11:28:26 +01:00 • committed by Cédric Le Goater
parent c52887687e
commit a23a72dd1e
2 changed files with 31 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

21
docs/specs/ppc-spapr-hcalls.rst
View file

@ -1,13 +1,12 @@
======================
sPAPR hypervisor calls sPAPR hypervisor calls
---------------------- ======================
When used with the ``pseries`` machine type, ``qemu-system-ppc64`` implements When used with the ``pseries`` machine type, ``qemu-system-ppc64`` implements
a set of hypervisor calls (a.k.a. hcalls) defined in the `Linux on Power a set of hypervisor calls (a.k.a. hcalls) defined in the Linux on Power
Architecture Reference document (LoPAR) Architecture Reference ([LoPAR]_) document. This document is a subset of the
<https://cdn.openpowerfoundation.org/wp-content/uploads/2020/07/LoPAR-20200812.pdf>`_. Power Architecture Platform Reference (PAPR+) specification (IBM internal only),
This document is a subset of the Power Architecture Platform Reference (PAPR+) which is what PowerVM, the IBM proprietary hypervisor, adheres to.
specification (IBM internal only), which is what PowerVM, the IBM proprietary
hypervisor, adheres to.
The subset in LoPAR is selected based on the requirements of Linux as a guest. The subset in LoPAR is selected based on the requirements of Linux as a guest.
@ -18,8 +17,8 @@ running in the guest and QEMU.
All those hypercalls start at hcall number 0xf000 which correspond All those hypercalls start at hcall number 0xf000 which correspond
to an implementation specific range in PAPR. to an implementation specific range in PAPR.
H_RTAS (0xf000) ``H_RTAS (0xf000)``
^^^^^^^^^^^^^^^ ===================
RTAS stands for Run-Time Abstraction Sercies and is a set of runtime services RTAS stands for Run-Time Abstraction Sercies and is a set of runtime services
generally provided by the firmware inside the guest to the operating system. It generally provided by the firmware inside the guest to the operating system. It
@ -44,8 +43,8 @@ Returns:
``H_PARAMETER``: Unknown token. ``H_PARAMETER``: Unknown token.
H_LOGICAL_MEMOP (0xf001) ``H_LOGICAL_MEMOP (0xf001)``
^^^^^^^^^^^^^^^^^^^^^^^^ ============================
When the guest runs in "real mode" (in powerpc terminology this means with MMU When the guest runs in "real mode" (in powerpc terminology this means with MMU
disabled, i.e. guest effective address equals to guest physical address), it disabled, i.e. guest effective address equals to guest physical address), it

42
docs/system/ppc/pseries.rst
View file

@ -1,19 +1,18 @@
===================================
pSeries family boards (``pseries``) pSeries family boards (``pseries``)
=================================== ===================================
The Power machine para-virtualized environment described by the `Linux on Power The Power machine para-virtualized environment described by the Linux on Power
Architecture Reference document (LoPAR) Architecture Reference ([LoPAR]_) document is called pSeries. This environment
<https://openpowerfoundation.org/wp-content/uploads/2020/07/LoPAR-20200812.pdf>`_ is also known as sPAPR, System p guests, or simply Power Linux guests (although
is called pSeries. This environment is also known as sPAPR, System p guests, or it is capable of running other operating systems, such as AIX).
simply Power Linux guests (although it is capable of running other operating
systems, such as AIX).
Even though pSeries is designed to behave as a guest environment, it is also Even though pSeries is designed to behave as a guest environment, it is also
capable of acting as a hypervisor OS, providing, on that role, nested capable of acting as a hypervisor OS, providing, on that role, nested
virtualization capabilities. virtualization capabilities.
Supported devices Supported devices
----------------- =================
* Multi processor support for many Power processors generations: POWER7, * Multi processor support for many Power processors generations: POWER7,
POWER7+, POWER8, POWER8NVL, POWER9, and Power10. Support for POWER5+ exists, POWER7+, POWER8, POWER8NVL, POWER9, and Power10. Support for POWER5+ exists,
@ -26,12 +25,12 @@ Supported devices
* PCIe device pass through. * PCIe device pass through.
Missing devices Missing devices
--------------- ===============
* SPICE support. * SPICE support.
Firmware Firmware
-------- ========
`SLOF <https://github.com/aik/SLOF>`_ (Slimline Open Firmware) is an `SLOF <https://github.com/aik/SLOF>`_ (Slimline Open Firmware) is an
implementation of the `IEEE 1275-1994, Standard for Boot (Initialization implementation of the `IEEE 1275-1994, Standard for Boot (Initialization
@ -42,14 +41,14 @@ QEMU includes a prebuilt image of SLOF which is updated when a more recent
version is required. version is required.
Build directions Build directions
---------------- ================
.. code-block:: bash .. code-block:: bash
./configure --target-list=ppc64-softmmu && make ./configure --target-list=ppc64-softmmu && make
Running instructions Running instructions
-------------------- ====================
Someone can select the pSeries machine type by running QEMU with the following Someone can select the pSeries machine type by running QEMU with the following
options: options:
@ -59,7 +58,7 @@ options:
qemu-system-ppc64 -M pseries <other QEMU arguments> qemu-system-ppc64 -M pseries <other QEMU arguments>
sPAPR devices sPAPR devices
------------- =============
The sPAPR specification defines a set of para-virtualized devices, which are The sPAPR specification defines a set of para-virtualized devices, which are
also supported by the pSeries machine in QEMU and can be instantiated with the also supported by the pSeries machine in QEMU and can be instantiated with the
@ -102,11 +101,9 @@ device, or specify one with an ID
NVRAM device with ``-global spapr-nvram.drive=pfid``. NVRAM device with ``-global spapr-nvram.drive=pfid``.
sPAPR specification sPAPR specification
^^^^^^^^^^^^^^^^^^^ -------------------
The main source of documentation on the sPAPR standard is the `Linux on Power The main source of documentation on the sPAPR standard is the [LoPAR]_ document.
Architecture Reference document (LoPAR)
<https://openpowerfoundation.org/wp-content/uploads/2020/07/LoPAR-20200812.pdf>`_.
However, documentation specific to QEMU's implementation of the specification However, documentation specific to QEMU's implementation of the specification
can also be found in QEMU documentation: can also be found in QEMU documentation:
@ -124,7 +121,7 @@ Other documentation available in QEMU docs directory:
(``/docs/specs/ppc-spapr-uv-hcalls.txt``). (``/docs/specs/ppc-spapr-uv-hcalls.txt``).
Switching between the KVM-PR and KVM-HV kernel module Switching between the KVM-PR and KVM-HV kernel module
----------------------------------------------------- =====================================================
Currently, there are two implementations of KVM on Power, ``kvm_hv.ko`` and Currently, there are two implementations of KVM on Power, ``kvm_hv.ko`` and
``kvm_pr.ko``. ``kvm_pr.ko``.
@ -139,7 +136,7 @@ possible to switch between the two modes with the ``kvm-type`` parameter:
instead. instead.
KVM-PR KVM-PR
^^^^^^ ------
KVM-PR uses the so-called **PR**\ oblem state of the PPC CPUs to run the guests, KVM-PR uses the so-called **PR**\ oblem state of the PPC CPUs to run the guests,
i.e. the virtual machine is run in user mode and all privileged instructions i.e. the virtual machine is run in user mode and all privileged instructions
@ -166,7 +163,7 @@ In order to run KVM-PR guests with POWER9 processors, someone will need to start
QEMU with ``kernel_irqchip=off`` command line option. QEMU with ``kernel_irqchip=off`` command line option.
KVM-HV KVM-HV
^^^^^^ ------
KVM-HV uses the hypervisor mode of more recent Power processors, that allow KVM-HV uses the hypervisor mode of more recent Power processors, that allow
access to the bare metal hardware directly. Although POWER7 had this capability, access to the bare metal hardware directly. Although POWER7 had this capability,
@ -188,7 +185,7 @@ CPUs generations, e.g. you can run a POWER7 guest on a POWER8 host by using
``-cpu POWER8,compat=power7`` as parameter to QEMU. ``-cpu POWER8,compat=power7`` as parameter to QEMU.
Modules support Modules support
--------------- ===============
As noticed in the sections above, each module can run in a different As noticed in the sections above, each module can run in a different
environment. The following table shows with which environment each module can environment. The following table shows with which environment each module can
@ -264,8 +261,11 @@ enabled, whether or not the guest has actually entered secure mode.
Maintainer contact information Maintainer contact information
------------------------------ ==============================
Cédric Le Goater <clg@kaod.org> Cédric Le Goater <clg@kaod.org>
Daniel Henrique Barboza <danielhb413@gmail.com> Daniel Henrique Barboza <danielhb413@gmail.com>
.. [LoPAR] `Linux on Power Architecture Reference document (LoPAR) revision
2.9 <https://openpowerfoundation.org/wp-content/uploads/2020/07/LoPAR-20200812.pdf>`_.