diff options
| author | Vitaly Kuznetsov <[email protected]> | 2021-05-26 15:20:22 +0200 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2021-06-17 13:09:49 -0400 |
| commit | d6bf71a18c74de61548ddad44ff95306fe85f829 (patch) | |
| tree | a433c113654fb296670ca8979f4c72408e7fc755 /tools/perf/scripts/python | |
| parent | 3b19b81acf300a3d452aa07b21d8db528254cb56 (diff) | |
KVM: nVMX: Ignore 'hv_clean_fields' data when eVMCS data is copied in vmx_get_nested_state()
'Clean fields' data from enlightened VMCS is only valid upon vmentry: L1
hypervisor is not obliged to keep it up-to-date while it is mangling L2's
state, KVM_GET_NESTED_STATE request may come at a wrong moment when actual
eVMCS changes are unsynchronized with 'hv_clean_fields'. As upon migration
VMCS12 is used as a source of ultimate truth, we must make sure we pick all
the changes to eVMCS and thus 'clean fields' data must be ignored.
Signed-off-by: Vitaly Kuznetsov <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Message-Id: <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions