From f58f084e71c6aeee066a30fc87422820e94a6cfc Mon Sep 17 00:00:00 2001 From: Cornelia Huck Date: Wed, 18 Mar 2020 11:39:40 +0100 Subject: Documentation: create/move s390x documentation Create a subdirectory for s390x under docs/system/ and move the existing vfio-ap documentation there. Create an initial document describing s390x system emulation. Suggested-by: Peter Maydell Signed-off-by: Cornelia Huck Acked-by: Christian Borntraeger Message-Id: <20200318103940.1169-1-cohuck@redhat.com> --- docs/system/target-s390x.rst | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 docs/system/target-s390x.rst (limited to 'docs/system/target-s390x.rst') diff --git a/docs/system/target-s390x.rst b/docs/system/target-s390x.rst new file mode 100644 index 0000000000..4c8b7cdd66 --- /dev/null +++ b/docs/system/target-s390x.rst @@ -0,0 +1,26 @@ +.. _s390x-System-emulator: + +s390x System emulator +--------------------- + +QEMU can emulate z/Architecture (in particular, 64 bit) s390x systems +via the ``qemu-system-s390x`` binary. Only one machine type, +``s390-ccw-virtio``, is supported (with versioning for compatibility +handling). + +When using KVM as accelerator, QEMU can emulate CPUs up to the generation +of the host. When using the default cpu model with TCG as accelerator, +QEMU will emulate a subset of z13 cpu features that should be enough to run +distributions built for the z13. + +Device support +============== + +QEMU will not emulate most of the traditional devices found under LPAR or +z/VM; virtio devices (especially using virtio-ccw) make up the bulk of +the available devices. Passthrough of host devices via vfio-pci, vfio-ccw, +or vfio-ap is also available. + +.. toctree:: + s390x/vfio-ap + -- cgit v1.2.3