linux-toradex.git/arch/x86/include/asm/vmx.h, branch v3.4.97

KVM: APIC: avoid instruction emulation for EOI writes

2011-09-25T16:52:17+00:00

Instruction emulation for EOI writes can be skipped, since sane
guest simply uses MOV instead of string operations. This is a nice
improvement when guest doesn't support x2apic or hyper-V EOI
support.

a single VM bandwidth is observed with ~8% bandwidth improvement
(7.4Gbps->8Gbps), by saving ~5% cycles from EOI emulation.

Signed-off-by: Kevin Tian 
:
Signed-off-by: Eddie Dong 
Signed-off-by: Marcelo Tosatti 
Signed-off-by: Avi Kivity

KVM: nVMX: vmcs12 checks on nested entry

2011-07-12T08:45:16+00:00

This patch adds a bunch of tests of the validity of the vmcs12 fields,
according to what the VMX spec and our implementation allows. If fields
we cannot (or don't want to) honor are discovered, an entry failure is
emulated.

According to the spec, there are two types of entry failures: If the problem
was in vmcs12's host state or control fields, the VMLAUNCH instruction simply
fails. But a problem is found in the guest state, the behavior is more
similar to that of an exit.

Signed-off-by: Nadav Har'El 
Signed-off-by: Marcelo Tosatti

KVM: nVMX: Exiting from L2 to L1

2011-07-12T08:45:16+00:00

This patch implements nested_vmx_vmexit(), called when the nested L2 guest
exits and we want to run its L1 parent and let it handle this exit.

Note that this will not necessarily be called on every L2 exit. L0 may decide
to handle a particular exit on its own, without L1's involvement; In that
case, L0 will handle the exit, and resume running L2, without running L1 and
without calling nested_vmx_vmexit(). The logic for deciding whether to handle
a particular exit in L1 or in L0, i.e., whether to call nested_vmx_vmexit(),
will appear in a separate patch below.

Signed-off-by: Nadav Har'El 
Signed-off-by: Marcelo Tosatti

KVM: nVMX: Success/failure of VMX instructions.

2011-07-12T08:45:12+00:00

VMX instructions specify success or failure by setting certain RFLAGS bits.
This patch contains common functions to do this, and they will be used in
the following patches which emulate the various VMX instructions.

Signed-off-by: Nadav Har'El 
Signed-off-by: Marcelo Tosatti

KVM: VMX: Add definitions for more vm entry/exit control bits

2011-01-12T09:31:08+00:00

Signed-off-by: Avi Kivity 
Signed-off-by: Marcelo Tosatti

KVM: VMX: add module parameter to avoid trapping HLT instructions (v5)

2011-01-12T09:30:46+00:00

In certain use-cases, we want to allocate guests fixed time slices where idle
guest cycles leave the machine idling.  There are many approaches to achieve
this but the most direct is to simply avoid trapping the HLT instruction which
lets the guest directly execute the instruction putting the processor to sleep.

Introduce this as a module-level option for kvm-vmx.ko since if you do this
for one guest, you probably want to do it for all.

Signed-off-by: Anthony Liguori 
Signed-off-by: Avi Kivity

KVM: handle exit due to INVD in VMX

2011-01-12T09:28:53+00:00

Currently the exit is unhandled, so guest halts with error if it tries
to execute INVD instruction. Call into emulator when INVD instruction
is executed by a guest instead. This instruction is not needed by ordinary
guests, but firmware (like OpenBIOS) use it and fail.

Signed-off-by: Gleb Natapov 
Signed-off-by: Marcelo Tosatti

KVM: VMX: Enable XSAVE/XRSTOR for guest

2010-08-01T07:46:31+00:00

This patch enable guest to use XSAVE/XRSTOR instructions.

We assume that host_xcr0 would use all possible bits that OS supported.

And we loaded xcr0 in the same way we handled fpu - do it as late as we can.

Signed-off-by: Dexuan Cui 
Signed-off-by: Sheng Yang 
Reviewed-by: Marcelo Tosatti 
Signed-off-by: Avi Kivity

KVM: VMX: Add all-context INVVPID type support

2010-08-01T07:46:04+00:00

Add all-context INVVPID type support.

Signed-off-by: Gui Jianfeng 
Signed-off-by: Avi Kivity

KVM: VMX: Make sure single type invvpid is supported before issuing invvpid instruction

2010-08-01T07:39:26+00:00

According to SDM, we need check whether single-context INVVPID type is supported
before issuing invvpid instruction.

Signed-off-by: Gui Jianfeng 
Reviewed-by: Sheng Yang 
Signed-off-by: Marcelo Tosatti