| commit | 55b1b753dff022dcc95123bed35946b4977d31fa | |
| author | David Hildenbrand <dahi@linux.vnet.ibm.com> | |
| Tue, 23 Jun 2015 07:10:51 +0000 (23 09:10 +0200) | ||
| committer | Cornelia Huck <cornelia.huck@de.ibm.com> | |
| Thu, 2 Jul 2015 13:35:33 +0000 (2 15:35 +0200) | ||
| tree | 7854c892d57bdfa181b1b68840adc69d81976535 | treesnapshot (tar.gz zip) |
| parent | 6efd2c2a125b4369b8def585b0dac35c849b5eb3 | commitdiff |
s390x/gdb: synchronize cpu state after modifying acrs
Whenever we touch the access control registers, we have to make sure that
the values will make it into kvm. Otherwise the change will simply be lost.
When synchronizing qemu and kvm, a normal KVM_PUT_RUNTIME_STATE does not take
care of these registers. Let's simply trigger a KVM_PUT_FULL_STATE sync,
so the values will directly be written to kvm. The performance overhead can
be ignored and this is much cleaner than manually writing these registers to kvm
via our two supported ways.
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Whenever we touch the access control registers, we have to make sure that
the values will make it into kvm. Otherwise the change will simply be lost.
When synchronizing qemu and kvm, a normal KVM_PUT_RUNTIME_STATE does not take
care of these registers. Let's simply trigger a KVM_PUT_FULL_STATE sync,
so the values will directly be written to kvm. The performance overhead can
be ignored and this is much cleaner than manually writing these registers to kvm
via our two supported ways.
Reviewed-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: David Hildenbrand <dahi@linux.vnet.ibm.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
| target-s390x/gdbstub.c | diffblobblamehistory |