diff options
| author |   Vitaly Kuznetsov <vkuznets@redhat.com> | 2020-03-09 16:52:13 +0100 |
|---|---|---|
| committer |   Paolo Bonzini <pbonzini@redhat.com> | 2020-03-16 18:19:30 +0100 |
| commit | b6a0653ae2cd71a58f479b46ff20307dd3540d63 (patch) | |
| tree | f18c9b0c24fd51d391bd77080639960efcab9ff7 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | KVM: nVMX: stop abusing need_vmcs12_to_shadow_sync for eVMCS mapping (diff) | |
| download | linux-dev-b6a0653ae2cd71a58f479b46ff20307dd3540d63.tar.xz linux-dev-b6a0653ae2cd71a58f479b46ff20307dd3540d63.zip | |
KVM: nVMX: properly handle errors in nested_vmx_handle_enlightened_vmptrld()
nested_vmx_handle_enlightened_vmptrld() fails in two cases:
- when we fail to kvm_vcpu_map() the supplied GPA
- when revision_id is incorrect.
Genuine Hyper-V raises #UD in the former case (at least with *some*
incorrect GPAs) and does VMfailInvalid() in the later. KVM doesn't do
anything so L1 just gets stuck retrying the same faulty VMLAUNCH.
nested_vmx_handle_enlightened_vmptrld() has two call sites:
nested_vmx_run() and nested_get_vmcs12_pages(). The former needs to queue
do much: the failure there happens after migration when L2 was running (and
L1 did something weird like wrote to VP assist page from a different vCPU),
just kill L1 with KVM_EXIT_INTERNAL_ERROR.
Reported-by: Miaohe Lin <linmiaohe@huawei.com>
Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
[Squash kbuild autopatch. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions