diff options
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | 2016-09-05 10:52:23 +0200 |
|---|---|---|
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | 2016-09-06 17:06:50 +0200 |
| commit | ad5afd07b628cd0610ea322ad60b5ad03aa250c8 (patch) | |
| tree | b9cc528d64e1039eeb365b3079042c0847d7dc2b /target-s390x/cpu.h | |
| parent | 6c064de1e08f425e2852ea9b38ea0723994aa4fd (diff) | |
| download | qemu-ad5afd07b628cd0610ea322ad60b5ad03aa250c8.tar.gz qemu-ad5afd07b628cd0610ea322ad60b5ad03aa250c8.tar.bz2 qemu-ad5afd07b628cd0610ea322ad60b5ad03aa250c8.zip | |
s390x/cpumodel: store the CPU model in the CPU instance
A CPU model consists of a CPU definition, to which delta changes are
applied - features added or removed (e.g. z13-base,vx=on). In addition,
certain properties (e.g. cpu id) can later on change during migration
but belong into the CPU model. This data will later be filled from the
host model in the KVM case.
Therefore, store the configured CPU model inside the CPU instance, so
we can later on perform delta changes using properties.
For the "qemu" model, we emulate in TCG a z900. "host" will be
uninitialized (cpu->model == NULL) unless we have CPU model support in KVM
later on. The other models are all initialized from their definitions.
Only the "host" model can have a cpu->model == NULL.
Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Message-Id: <20160905085244.99980-10-dahi@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Diffstat (limited to 'target-s390x/cpu.h')
| -rw-r--r-- | target-s390x/cpu.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/target-s390x/cpu.h b/target-s390x/cpu.h index 4f14632928..95601bc907 100644 --- a/target-s390x/cpu.h +++ b/target-s390x/cpu.h @@ -188,6 +188,7 @@ struct S390CPU { CPUS390XState env; int64_t id; + S390CPUModel *model; /* needed for live migration */ void *irqstate; uint32_t irqstate_saved_size; |