| commit | b2ac0ff5d9478907cfd5b204c9179f77d0cb943f | |
| author | Eric Farman <farman@linux.vnet.ibm.com> | |
| Thu, 7 May 2015 14:52:16 +0000 (7 10:52 -0400) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Wed, 27 May 2015 15:52:03 +0000 (27 17:52 +0200) | ||
| tree | ed72a923a6e26cb8527e2d31d337e47d1d278b13 | treesnapshot (tar.gz zip) |
| parent | 3ceeb2930faf1116ee4bb22c8a7794bb2337e8a9 | commitdiff |
s390x: Migrate vector registers
When migrating a guest, be sure to include the vector registers.
The vector registers are defined in a subsection, similar to the
existing subsection for floating point registers. Since the
floating point registers are always present (and thus migrated),
we can skip them when performing the migration of the vector
registers which may or may not be present.
Suggested-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Eric Farman <farman@linux.vnet.ibm.com>
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
When migrating a guest, be sure to include the vector registers.
The vector registers are defined in a subsection, similar to the
existing subsection for floating point registers. Since the
floating point registers are always present (and thus migrated),
we can skip them when performing the migration of the vector
registers which may or may not be present.
Suggested-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Eric Farman <farman@linux.vnet.ibm.com>
Reviewed-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| target-s390x/cpu.h | diffblobblamehistory | |
| target-s390x/machine.c | diffblobblamehistory |