Sean Christopherson 34333cc6c2 KVM: nVMX: Ignore limit checks on VMX instructions using flat segments ... Regarding segments with a limit==0xffffffff, the SDM officially states: When the effective limit is FFFFFFFFH (4 GBytes), these accesses may or may not cause the indicated exceptions. Behavior is implementation-specific and may vary from one execution to another. In practice, all CPUs that support VMX ignore limit checks for "flat segments", i.e. an expand-up data or code segment with base=0 and limit=0xffffffff. This is subtly different than wrapping the effective address calculation based on the address size, as the flat segment behavior also applies to accesses that would wrap the 4g boundary, e.g. a 4-byte access starting at 0xffffffff will access linear addresses 0xffffffff, 0x0, 0x1 and 0x2. Fixes: f9eb4af67c ("KVM: nVMX: VMX instructions: add checks for #GP/#SS exceptions") Cc: stable@vger.kernel.org Signed-off-by: Sean Christopherson <sean.j.christopherson@intel.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2019-02-20 22:48:24 +01:00
..
capabilities.h
evmcs.c	x86/kvm/hyper-v: nested_enable_evmcs() sets vmcs_version incorrectly	2019-01-25 19:11:37 +01:00
evmcs.h
nested.c	KVM: nVMX: Ignore limit checks on VMX instructions using flat segments	2019-02-20 22:48:24 +01:00
nested.h
ops.h
pmu_intel.c
vmcs12.c
vmcs12.h
vmcs_shadow_fields.h
vmcs.h	KVM: nVMX: Cache host_rsp on a per-VMCS basis	2019-02-12 13:12:22 +01:00
vmenter.S	KVM: VMX: Reorder clearing of registers in the vCPU-run assembly flow	2019-02-20 22:48:18 +01:00
vmx.c	KVM: VMX: Call vCPU-run asm sub-routine from C and remove clobbering	2019-02-20 22:48:18 +01:00
vmx.h	KVM: VMX: Pass "launched" directly to the vCPU-run asm blob	2019-02-12 13:12:24 +01:00