diff options
| author | Suraj Jitindar Singh <sjitindarsingh@gmail.com> | 2018-01-12 16:33:43 +1100 |
|---|---|---|
| committer | David Gibson <david@gibson.dropbear.id.au> | 2018-01-17 09:35:24 +1100 |
| commit | 4e5fe3688e23d61b45cc549ff1322aff8f50ef45 (patch) | |
| tree | 79fac90a82477231956cee7d1c4b760a3fa9860a /bsd-user | |
| parent | 2d1fb9bc8e6e78931d8e1bfeb0ed7a4d223b0480 (diff) | |
| download | qemu-4e5fe3688e23d61b45cc549ff1322aff8f50ef45.zip qemu-4e5fe3688e23d61b45cc549ff1322aff8f50ef45.tar.gz qemu-4e5fe3688e23d61b45cc549ff1322aff8f50ef45.tar.bz2 | |
hw/ppc/spapr_caps: Rework spapr_caps to use uint8 internal representation
Currently spapr_caps are tied to boolean values (on or off). This patch
reworks the caps so that they can have any uint8 value. This allows more
capabilities with various values to be represented in the same way
internally. Capabilities are numbered in ascending order. The internal
representation of capability values is an array of uint8s in the
sPAPRMachineState, indexed by capability number.
Capabilities can have their own name, description, options, getter and
setter functions, type and allow functions. They also each have their own
section in the migration stream. Capabilities are only migrated if they
were explictly set on the command line, with the assumption that
otherwise the default will match.
On migration we ensure that the capability value on the destination
is greater than or equal to the capability value from the source. So
long at this remains the case then the migration is considered
compatible and allowed to continue.
This patch implements generic getter and setter functions for boolean
capabilities. It also converts the existings cap-htm, cap-vsx and
cap-dfp capabilities to this new format.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'bsd-user')
0 files changed, 0 insertions, 0 deletions