Re: [Qemu-devel] [0/27] Implement emulation of pSeries logical partitions (v6)

[Anthony Liguori]

On 03/31/2011 11:15 PM, David Gibson wrote:
> This patch series adds a "pseries" machine to qemu, allowing it to
> emulate IBM pSeries logical partitions.  More specifically it
> implements the interface defined by the "PowerPC Architecture Platform
> Requirements" document (PAPR, or sPAPR for short).
>
> Along the way we add a bunch of support for more modern ppc CPUs than
> are currently supported.  It also makes some significant cleanups to
> the translation code for hash page table based ppc MMUs.
>
> Please apply.

So what's a typical invocation for this?  Is:

qemu-system-ppc64 -m pseries foo.img -nographics

Enough or is something more sophisticated required?

Regards,

Anthony Liguori

> ---
>
> Changes since v5 of this series:
>   * Include source for SLOF as a git submodule
>   * Move our private hcalls (well. only one so far) to a range
>     explicitly reserved by PAPR for this purpose.
>   * Allocate an ample 1024 irqs in the XICS controller, rather than
>     having a somewhat dubious calculation of precisely how many we
>     need.
>
> Changes since v4 of this series:
>   * Fix build breakages for powerpc targets other than ppc64 full system.
>   * Since the pseries platform requires libfdt, only compile it when
>     configured with --enable-fdt
>   * Give an informative error if invoked with insufficient guest RAM to
>     run the partition firmware.  Without this, giving insufficient RAM
>     - such as qemu's default 64M - would lead to the firmware failing
>     cryptically partway through boot.
>
> Changes since v3 of this series:
>   * Many, many checkpatch fixups
>   * Integrated feedback from qemu-devel list
>   * Added in-partition SLOF firmware
>
> Changes since v2 of this series:
>   * Assorted bugfixes and cleanups.
>
> Changes since v1 of this series:
>   * numerous coding style fixups
>   * incorporated most review comments from initial version
>   * moved to a wholly dynamic hypercall registration scheme
>   * assorted other cleanups
>   * many more patches implementing VIO devices