This series is a first draft to add the notion of optional
capabilities to the "pseries" machine type. A default set of
capabilities is selected based on the machine type version and
selected cpu model, but this can be overridden with machine
parameters.
The purpose of this is to get rid of a number of places where we
implicitly decide what features to advertise to the guest based on
capabilities of the host. This is bad, because it means it's
difficult to be certain if machines started at different ends of a
migration really match from the guest's point of view.
By giving the user explicit control of these optional features, then
validating that the chosen ones can be supplied on the host we make
behaviour more predictable.
The more specific motivation for this is that POWER9 has bugs in its
hardware transactional memory (HTM) implementation making it unsafe to
migrate POWER8 guests to POWER9 if they use HTM.
Changes since RFC:
- Two preliminary patches not really related split off and already
merged.
- Assorted minor fixes based on review notes
- Change defaults to disable HTM on pseries-2.12 machine type
David Gibson (6):
spapr: Capabilities infrastructure
spapr: Treat Hardware Transactional Memory (HTM) as an optional
capability
spapr: Validate capabilities on migration
target/ppc: Clean up probing of VMX, VSX and DFP availability on KVM
spapr: Handle VMX/VSX presence as an spapr capability flag
spapr: Handle Decimal Floating Point (DFP) as an optional capability
hw/ppc/Makefile.objs | 2 +-
hw/ppc/spapr.c | 47 +++++--
hw/ppc/spapr_caps.c | 342 +++++++++++++++++++++++++++++++++++++++++++++++++
include/hw/ppc/spapr.h | 46 +++++++
target/ppc/kvm.c | 27 +---
target/ppc/kvm_ppc.h | 2 -
6 files changed, 429 insertions(+), 37 deletions(-)
create mode 100644 hw/ppc/spapr_caps.c
--
2.14.3
