diff options
| author | Ladi Prosek <[email protected]> | 2017-03-23 07:18:08 +0100 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2017-03-28 10:10:15 +0200 |
| commit | 7ad658b693536741c37b16aeb07840a2ce75f5b9 (patch) | |
| tree | 7b865d5e02a05db83e9684bafad0ebf5fe0e8ea3 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | 0292e169b2d9c8377a168778f0b16eadb1f578fd (diff) | |
KVM: nVMX: fix nested EPT detection
The nested_ept_enabled flag introduced in commit 7ca29de2136 was not
computed correctly. We are interested only in L1's EPT state, not the
the combined L0+L1 value.
In particular, if L0 uses EPT but L1 does not, nested_ept_enabled must
be false to make sure that PDPSTRs are loaded based on CR3 as usual,
because the special case described in 26.3.2.4 Loading Page-Directory-
Pointer-Table Entries does not apply.
Fixes: 7ca29de21362 ("KVM: nVMX: fix CR3 load if L2 uses PAE paging and EPT")
Cc: [email protected]
Reported-by: Wanpeng Li <[email protected]>
Reviewed-by: David Hildenbrand <[email protected]>
Signed-off-by: Ladi Prosek <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions