- 11 May, 2011 40 commits
-
-
Avi Kivity authored
So it can call emulate_gp() without forward declarations. Signed-off-by:Avi Kivity <avi@redhat.com>
-
Avi Kivity authored
Needed for segment read/write checks. Signed-off-by: -
Avi Kivity authored
Preparing to add segment checks. Signed-off-by: -
Avi Kivity authored
It's going to get more complicated soon. Signed-off-by: -
Avi Kivity authored
Will help later adding proper segment checks. Signed-off-by: -
Joerg Roedel authored
When the emulation of vmload or vmsave fails because the guest passed an unsupported physical address it gets an #GP with rip pointing to the instruction after vmsave/vmload. This is a bug and fixed by this patch. Signed-off-by:
Joerg Roedel <joerg.roedel@amd.com> Signed-off-by:
-
Joerg Roedel authored
This patch implements two new vm-ioctls to get and set the virtual_tsc_khz if the machine supports tsc-scaling. Setting the tsc-frequency is only possible before userspace creates any vcpu. Signed-off-by:
-
Joerg Roedel authored
With TSC scaling in SVM the tsc-offset needs to be calculated differently. This patch propagates this calculation into the architecture specific modules so that this complexity can be handled there. Signed-off-by:
-
Joerg Roedel authored
This patch implements a call-back into the architecture code to allow the propagation of changes to the virtual tsc_khz of the vcpu. On SVM it updates the tsc_ratio variable, on VMX it does nothing. Signed-off-by:
-
Joerg Roedel authored
The calculation of the tsc_delta value to ensure a forward-going tsc for the guest is a function of the host-tsc. This works as long as the guests tsc_khz is equal to the hosts tsc_khz. With tsc-scaling hardware support this is not longer true and the tsc_delta needs to be calculated using guest_tsc values. Signed-off-by:
-
Joerg Roedel authored
This patch changes the kvm_guest_time_update function to use TSC frequency the guest actually has for updating its clock. Signed-off-by:
-
Joerg Roedel authored
This patch enhances the kvm_amd module with functions to support the TSC_RATE_MSR which can be used to set a given tsc frequency for the guest vcpu. Signed-off-by:
-
Avi Kivity authored
VMMCALL requires EFER.SVME to be enabled in the host, not in the guest, which is what check_svme() checks. Signed-off-by: -
Avi Kivity authored
VMMCALL needs the VendorSpecific tag so that #UD emulation (called if a guest running on AMD was migrated to an Intel host) is allowed to process the instruction. Signed-off-by: -
Bharat Bhushan authored
Following dump is observed on host when clearing the exit timing counters [root@p1021mds kvm]# echo -n 'c' > vm1200_vcpu0_timing INFO: task echo:1276 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. echo D 0ff5bf94 0 1276 1190 0x00000000 Call Trace: [c2157e40] [c0007908] __switch_to+0x9c/0xc4 [c2157e50] [c040293c] schedule+0x1b4/0x3bc [c2157e90] [c04032dc] __mutex_lock_slowpath+0x74/0xc0 [c2157ec0] [c00369e4] kvmppc_init_timing_stats+0x20/0xb8 [c2157ed0] [c0036b00] kvmppc_exit_timing_write+0x84/0x98 [c2157ef0] [c00b9f90] vfs_write+0xc0/0x16c [c2157f10] [c00ba284] sys_write+0x4c/0x90 [c2157f40] [c000e320] ret_from_syscall+0x0/0x3c The vcpu->mutex is used by kvm_ioctl_* (KVM_RUN etc) and same was used when clearing the stats (in kvmppc_init_timing_stats()). What happens is that when the guest is idle then it held the vcpu->mutx. While the exiting timing process waits for guest to release the vcpu->mutex and a hang state is reached. Now using seprate lock for exit timing stats. Signed-off-by:Bharat Bhushan <Bharat.Bhushan@freescale.com> Acked-by:
Alexander Graf <agraf@suse.de> Signed-off-by:
-
Xiao Guangrong authored
The mmu_seq verification can be removed since we get the pfn in the protection of mmu_lock. Signed-off-by:
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com> Signed-off-by:
-
Gleb Natapov authored
Signed-off-by:
Gleb Natapov <gleb@redhat.com> Signed-off-by:
-
Justin P. Mattock authored
The patch below removes unsigned long base_addresss; in i8254.h since it is unused. Signed-off-by:
Justin P. Mattock <justinmattock@gmail.com> Signed-off-by:
-
Joerg Roedel authored
This patch removes all the old code which handled the nested selective cr0 write intercepts. This code was only in place as a work-around until the instruction emulator is capable of doing the same. This is the case with this patch-set and so the code can be removed. Signed-off-by:
-
Joerg Roedel authored
This patch adds code to check for IOIO intercepts on instructions decoded by the KVM instruction emulator. [avi: fix build error due to missing #define D2bvIP] Signed-off-by:
-
Joerg Roedel authored
This patch add intercept checks for emulated one-byte instructions to the KVM instruction emulation path. Signed-off-by:
-
Joerg Roedel authored
This patch adds intercepts checks for the remaining twobyte instructions to the KVM instruction emulator. Signed-off-by:
-
Joerg Roedel authored
This patch implements the emulator intercept checks for the RDTSCP, MONITOR, and MWAIT instructions. Signed-off-by:
-
Joerg Roedel authored
This patch adds the necessary code changes in the instruction emulator and the extensions to svm.c to implement intercept checks for the svm instructions. Signed-off-by:
-
Joerg Roedel authored
This patch add intercept checks into the KVM instruction emulator to check for the 8 instructions that access the descriptor table addresses. Signed-off-by:
-
Joerg Roedel authored
This patch adds the intercept checks for instruction accessing the debug registers. Signed-off-by:
-
Joerg Roedel authored
This patch adds all necessary intercept checks for instructions that access the crX registers. Signed-off-by:
-
Joerg Roedel authored
This patch adds a callback into kvm_x86_ops so that svm and vmx code can do intercept checks on emulated instructions. Signed-off-by:
-
Joerg Roedel authored
This patch adds a flag for the opcoded to tag instruction which are only recognized in protected mode. The necessary check is added too. Signed-off-by:
-
Joerg Roedel authored
This patch adds a check_perm callback for each opcode into the instruction emulator. This will be used to do all necessary permission checks on instructions before checking whether they are intercepted or not. Signed-off-by:
-
Joerg Roedel authored
This patch prevents the changed CPU state to be written back when the emulator detected that the instruction was intercepted by the guest. Signed-off-by:
-
Avi Kivity authored
Add intercept codes for instructions defined by SVM as interceptable. Signed-off-by:
-
Avi Kivity authored
When running in guest mode, certain instructions can be intercepted by hardware. This also holds for nested guests running on emulated virtualization hardware, in particular instructions emulated by kvm itself. This patch adds a framework for intercepting instructions. If an instruction is marked for interception, and if we're running in guest mode, a callback is called to check whether an intercept is needed or not. The callback is called at three points in time: immediately after beginning execution, after checking privilge exceptions, and after checking memory exception. This suits the different interception points defined for different instructions and for the various virtualization instruction sets. In addition, a new X86EMUL_INTERCEPT is defined, which any callback or memory access may define, allowing the more complicated intercepts to be implemented in existing callbacks. Signed-off-by:
-
Avi Kivity authored
Signed-off-by: -
Avi Kivity authored
Add support for marking an instruction as SSE, switching registers used to the SSE register file. Signed-off-by: -
Avi Kivity authored
Most SIMD instructions use the 66/f2/f3 prefixes to distinguish between different variants of the same instruction. Usually the encoding is quite regular, but in some cases (including non-SIMD instructions) the prefixes generate very different instructions. Examples include XCHG/PAUSE, MOVQ/MOVDQA/MOVDQU, and MOVBE/CRC32. Allow the emulator to handle these special cases by splitting such opcodes into groups, with different decode flags and execution functions for different prefixes. Signed-off-by: -
Avi Kivity authored
Needed for emulating fpu instructions. Signed-off-by: -
Avi Kivity authored
Currently we store a rep prefix as 1 or 2 depending on whether it is a REPE or REPNE. Since sse instructions depend on the prefix value, store it as the original opcode to simplify things further on. Signed-off-by: -
Avi Kivity authored
Since sse instructions can issue 16-byte mmios, we need to support them. We can't increase the kvm_run mmio buffer size to 16 bytes without breaking compatibility, so instead we break the large mmios into two smaller 8-byte ones. Since the bus is 64-bit we aren't breaking any atomicity guarantees. Signed-off-by: -
Avi Kivity authored
Make room for sse mmio completions. Signed-off-by:
-
