diff options
| author | David Hildenbrand | 2017-10-16 16:42:56 +0200 |
|---|---|---|
| committer | Paolo Bonzini | 2017-10-18 09:49:48 +0200 |
| commit | ae990e6cd77a4e6004b7abc6d293598910abca63 (patch) | |
| tree | 85659c1c063e5f03978b3d27173c3e2f91b9b193 /scripts | |
| parent | target/i386: trap on instructions longer than >15 bytes (diff) | |
| download | qemu-ae990e6cd77a4e6004b7abc6d293598910abca63.tar.gz qemu-ae990e6cd77a4e6004b7abc6d293598910abca63.tar.xz qemu-ae990e6cd77a4e6004b7abc6d293598910abca63.zip | |
memory: call log_start after region_add
It might be confusing for some listener implementations that implement
both, region_add and log_start (e.g. KVM) if we call log_start before an
actual region was added using region_add.
This makes current KVM code trigger an assertion
("kvm_section_update_flags: error finding slot"). So let's just reverse
the order instead of tolerating log_start on yet unknown regions.
Reported-by: Thomas Huth <thuth@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Message-Id: <20171016144302.24284-2-david@redhat.com>
Tested-by: Joe Clifford <joeclifford@gmail.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions