Shannon Zhao 6c090d4a75 kvm: Delete the slot if and only if the KVM_MEM_READONLY flag is changed ... According to KVM commit 75d61fbc, it needs to delete the slot before changing the KVM_MEM_READONLY flag. But QEMU commit 235e8982 only check whether KVM_MEM_READONLY flag is set instead of changing. It doesn't need to delete the slot if the KVM_MEM_READONLY flag is not changed. This fixes a issue that migrating a VM at the OVMF startup stage and VM is executing the codes in rom. Between the deleting and adding the slot in kvm_set_user_memory_region, there is a chance that guest access rom and trap to KVM, then KVM can't find the corresponding memslot. While KVM (on ARM) injects an abort to guest due to the broken hva, then guest will get stuck. Signed-off-by: Shannon Zhao <zhaoshenglong@huawei.com> Message-Id: <1526462314-19720-1-git-send-email-zhaoshenglong@huawei.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2018-06-28 19:05:31 +02:00
..
Makefile.objs	kvm: add memory encryption context	2018-03-13 12:04:03 +01:00
kvm-all.c	kvm: Delete the slot if and only if the KVM_MEM_READONLY flag is changed	2018-06-28 19:05:31 +02:00
sev-stub.c	kvm: introduce memory encryption APIs	2018-03-13 12:04:03 +01:00
trace-events	kvm: Add kvm_set_user_memory tracepoint	2018-02-05 13:54:38 +01:00