diff options
| author | Christian Borntraeger | 2017-03-07 15:19:08 +0100 |
|---|---|---|
| committer | Paolo Bonzini | 2017-03-14 13:26:36 +0100 |
| commit | 79ca7a1b898eb97c4192f3c78027a0f20485e7b4 (patch) | |
| tree | 5c60dbce59070b2b05076f6975d769938461f7b2 /scripts/simpletrace.py | |
| parent | mem-prealloc: reduce large guest start-up and migration time. (diff) | |
| download | qemu-79ca7a1b898eb97c4192f3c78027a0f20485e7b4.tar.gz qemu-79ca7a1b898eb97c4192f3c78027a0f20485e7b4.tar.xz qemu-79ca7a1b898eb97c4192f3c78027a0f20485e7b4.zip | |
exec: add cpu_synchronize_state to cpu_memory_rw_debug
I sometimes got "Cannot access memory" when using the x command
on the monitor. Turns out that the cpu env did contain stale data
(e.g. wrong control register content for page table origin).
We must synchronize the state of the CPU before walking the page
tables. A similar issues happens for a remote gdb, so lets
do the cpu_synchronize_state in cpu_memory_rw_debug.
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Message-Id: <1488896348-13560-1-git-send-email-borntraeger@de.ibm.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts/simpletrace.py')
0 files changed, 0 insertions, 0 deletions