- 24 Oct, 2010 40 commits
-
-
Jason Wang authored
Pit interrupt injection was done by workqueue, so no need to check pending pit timer in vcpu thread which could lead unnecessary unblocking of vcpu. Signed-off-by:
Jason Wang <jasowang@redhat.com> Signed-off-by:
Avi Kivity <avi@redhat.com>
-
Alexander Graf authored
When CONFIG_KVM_GUEST is selected, but CONFIG_KVM is not, we were missing some defines in asm-offsets.c and included too many headers at other places. This patch makes above configuration work. Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by:
Alexander Graf <agraf@suse.de> Signed-off-by:
-
Avi Kivity authored
The ALU opcode block is very regular; introduce D6ALU() to define decode flags for 6 instructions at a time. Suggested by Paolo Bonzini. Signed-off-by:
Marcelo Tosatti <mtosatti@redhat.com>
-
Avi Kivity authored
Use do_div() instead. Signed-off-by:
-
Avi Kivity authored
Signed-off-by:
-
Avi Kivity authored
Like DIV and IDIV. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Use the new byte/word dual opcode decode. Signed-off-by:
-
Avi Kivity authored
Many x86 instructions come in byte and word variants distinguished with bit 0 of the opcode. Add macros to aid in defining them. Signed-off-by:
-
Avi Kivity authored
SrcMemFAddr is not defined with the modrm operand designating a register instead of a memory address. Signed-off-by:
-
Gleb Natapov authored
x86_emulate_insn() will return 1 if instruction can be restarted without re-entering a guest. Signed-off-by:
Gleb Natapov <gleb@redhat.com> Signed-off-by:
-
Gleb Natapov authored
Signed-off-by:
-
Gleb Natapov authored
Signed-off-by:
-
Wei Yongjun authored
Signed-off-by:
Wei Yongjun <yjwei@cn.fujitsu.com> Signed-off-by:
-
Alexander Graf authored
As suggested by Christian, we should expose headers to user space with information that might be valuable there. The s390 virtio interface is one of those cases. It defines an ABI between hypervisor and guest, so it should be exposed to user space. Reported-by:
Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by:
-
Alexander Graf authored
The one big missing feature in s390-virtio was hotplugging. This is no more. This patch implements hotplug add support, so you can on the fly add new devices in the guest. Keep in mind that this needs a patch for qemu to actually leverage the functionality. Signed-off-by:
-
Alexander Graf authored
Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by:
-
Xiao Guangrong authored
Combine guest pte read between guest pte check in the fetch path and pte prefetch Signed-off-by:
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com> Signed-off-by:
-
Xiao Guangrong authored
Support prefetch ptes when intercept guest #PF, avoid to #PF by later access If we meet any failure in the prefetch path, we will exit it and not try other ptes to avoid become heavy path Signed-off-by:
-
Xiao Guangrong authored
Introduce this function to get consecutive gfn's pages, it can reduce gup's overload, used by later patch Signed-off-by:
-
Xiao Guangrong authored
Introduce hva_to_pfn_atomic(), it's the fast path and can used in atomic context, the later patch will use it Signed-off-by:
-
Xiao Guangrong authored
This function is used by KVM to pin process's page in the atomic context. Define the 'weak' function to avoid other architecture not support it Acked-by:
Nick Piggin <npiggin@suse.de> Signed-off-by:
-
Zachary Amsden authored
Basic informational document about x86 timekeeping and how KVM is affected. Signed-off-by:
Zachary Amsden <zamsden@redhat.com> Signed-off-by:
-
Zachary Amsden authored
Kernel time, which advances in discrete steps may progress much slower than TSC. As a result, when kvmclock is adjusted to a new base, the apparent time to the guest, which runs at a much higher, nsec scaled rate based on the current TSC, may have already been observed to have a larger value (kernel_ns + scaled tsc) than the value to which we are setting it (kernel_ns + 0). We must instead compute the clock as potentially observed by the guest for kernel_ns to make sure it does not go backwards. Signed-off-by:
-
Zachary Amsden authored
The scale_delta function for shift / multiply with 31-bit precision moves to a common header so it can be used by both kernel and kvm module. Signed-off-by:
-
Zachary Amsden authored
If there are active VCPUs which are marked as belonging to a particular hardware CPU, request a clock sync for them when enabling hardware; the TSC could be desynchronized on a newly arriving CPU, and we need to recompute guests system time relative to boot after a suspend event. This covers both cases. Note that it is acceptable to take the spinlock, as either no other tasks will be running and no locks held (BSP after resume), or other tasks will be guaranteed to drop the lock relatively quickly (AP on CPU_STARTING). Noting we now get clock synchronization requests for VCPUs which are starting up (or restarting), it is tempting to attempt to remove the arch/x86/kvm/x86.c CPU hot-notifiers at this time, however it is not correct to do so; they are required for systems with non-constant TSC as the frequency may not be known immediately after the processor has started until the cpufreq driver has had a chance to run and query the chipset. Updated: implement better locking semantics for hardware_enable Removed the hack of dropping and retaking the lock by adding the semantic that we always hold kvm_lock when hardware_enable is called. The one place that doesn't need to worry about it is resume, as resuming a frozen CPU, the spinlock won't be taken. Signed-off-by:
-
Zachary Amsden authored
Make the match of TSC find TSC writes that are close to each other instead of perfectly identical; this allows the compensator to also work in migration / suspend scenarios. Signed-off-by:
-
Zachary Amsden authored
Add a helper function to compute the kernel time and convert nanoseconds back to CPU specific cycles. Note that these must not be called in preemptible context, as that would mean the kernel could enter software suspend state, which would cause non-atomic operation. Also, convert the KVM_SET_CLOCK / KVM_GET_CLOCK ioctls to use the kernel time helper, these should be bootbased as well. Signed-off-by:
-
Zachary Amsden authored
When CPUs with unstable TSCs enter deep C-state, TSC may stop running. This causes us to require resynchronization. Since we can't tell when this may potentially happen, we assume the worst by forcing re-compensation for it at every point the VCPU task is descheduled. Signed-off-by:
-
Zachary Amsden authored
Move the TSC control logic from the vendor backends into x86.c by adding adjust_tsc_offset to x86 ops. Now all TSC decisions can be done in one place. Signed-off-by:
-
Zachary Amsden authored
If creating an SMP guest with unstable host TSC, issue a warning Signed-off-by:
-
Zachary Amsden authored
This simplifies much of the init code; we can now simply always call tsc_khz_changed, optionally passing it a new value, or letting it figure out the existing value (while interrupts are disabled, and thus, by inference from the rule, not raceful against CPU hotplug or frequency updates, which will issue IPIs to the local CPU to perform this very same task). Signed-off-by:
-
Zachary Amsden authored
Attempt to synchronize TSCs which are reset to the same value. In the case of a reliable hardware TSC, we can just re-use the same offset, but on non-reliable hardware, we can get closer by adjusting the offset to match the elapsed time. Signed-off-by:
-
Zachary Amsden authored
Also, ensure that the storing of the offset and the reading of the TSC are never preempted by taking a spinlock. While the lock is overkill now, it is useful later in this patch series. Signed-off-by:
-
Zachary Amsden authored
Change svm / vmx to be the same internally and write TSC offset instead of bare TSC in helper functions. Isolated as a single patch to contain code movement. Signed-off-by:
-
