- 10 Sep, 2009 40 commits
-
-
Gleb Natapov authored
No need to call it before each kvm_(set|get)_msr_common() Signed-off-by:
Gleb Natapov <gleb@redhat.com> Signed-off-by:
Marcelo Tosatti <mtosatti@redhat.com>
-
Avi Kivity authored
Only reload debug register 6 if we're running with the guest's debug registers. Saves around 150 cycles from the guest lightweight exit path. dr6 contains a couple of bits that are updated on #DB, so intercept that unconditionally and update those bits then. Signed-off-by:
Avi Kivity <avi@redhat.com> Signed-off-by:
-
Avi Kivity authored
Instead of saving the debug registers from the processor to a kvm data structure, rely in the debug registers stored in the thread structure. This allows us not to save dr6 and dr7. Reduces lightweight vmexit cost by 350 cycles, or 11 percent. Signed-off-by: -
Marcelo Tosatti authored
Commit b8bcfe99 made paravirt pte updates synchronous in interrupt context. Unfortunately the KVM pv mmu code caches the lazy/nonlazy mode internally, so a pte update from interrupt context during a lazy mmu operation can be batched while it should be performed synchronously. https://bugzilla.redhat.com/show_bug.cgi?id=518022 Drop the internal mode variable and use paravirt_get_lazy_mode(), which returns the correct state. Cc: stable@kernel.org Signed-off-by:
-
Gleb Natapov authored
This bug was introduced by b4a2f5e7. Cc: stable@kernel.org Signed-off-by:
-
Glauber Costa authored
The use of __pa() to calculate the address of a C-visible symbol is wrong, and can lead to unpredictable results. See arch/x86/include/asm/page.h for details. It should be replaced with __pa_symbol(), that does the correct math here, by taking relocations into account. This ensures the correct wallclock data structure physical address is passed to the hypervisor. Cc: stable@kernel.org Signed-off-by:
Glauber Costa <glommer@redhat.com> Signed-off-by:
-
Gleb Natapov authored
Don't call adjust_vmx_controls() two times for the same control. It restores options that were dropped earlier. This loses us the cr8 exit control, which causes a massive performance regression Windows x64. Cc: stable@kernel.org Signed-off-by:
-
Avi Kivity authored
We know no pages are protected, so we can short-circuit the whole thing (including fairly nasty guest memory accesses). Signed-off-by: -
Avi Kivity authored
Signed-off-by: -
Avi Kivity authored
update_cr8_intercept() can be triggered from userspace while there is no apic present. Signed-off-by: -
Sheng Yang authored
QNX update WP bit when paging enabled, which is not covered yet. This one fix QNX boot with EPT. Cc: stable@kernel.org Signed-off-by:
Sheng Yang <sheng@linux.intel.com> Signed-off-by:
-
Mikhail Ershov authored
Segment descriptors tables can be placed on two non-contiguous pages. This patch makes reading segment descriptors by linear address. Signed-off-by:
Mikhail Ershov <Mike.Ershov@gmail.com> Signed-off-by:
-
Mohammed Gamal authored
Add missing decoder flags for adc and sbb instructions (opcodes 0x14-0x15, 0x1c-0x1d) Signed-off-by:
Mohammed Gamal <m.gamal005@gmail.com> Signed-off-by:
-
Avi Kivity authored
Signed-off-by: -
Avi Kivity authored
Signed-off-by: -
Michael S. Tsirkin authored
kvm_para.h contains userspace interface and so should be exported. Signed-off-by:
Michael S. Tsirkin <mst@redhat.com> Signed-off-by:
-
Amit Shah authored
The KVM list moved to vger.kernel.org last year Signed-off-by:
Amit Shah <amit.shah@redhat.com> Signed-off-by:
-
Avi Kivity authored
We're in arch/x86, what could we possibly be emulating? Signed-off-by: -
Anthony Liguori authored
According to 16.2.5 in the SDM, eflags.vm in the tss is consulted before loading and new segments. If eflags.vm == 1, then the segments are treated as 16-bit segments. The LDTR and TR are not normally available in vm86 mode so if they happen to somehow get loaded, they need to be treated as 32-bit segments. This fixes an invalid vmentry failure in a custom OS that was happening after a task switch into vm8086 mode. Since the segments were being mistakenly treated as 32-bit, we loaded garbage state. Signed-off-by:
Anthony Liguori <aliguori@us.ibm.com> Signed-off-by:
-
Avi Kivity authored
We set rflags.vm86 when virtualizing real mode to do through vm8086 mode; so we need to take it out again when reading rflags. Signed-off-by: -
Avi Kivity authored
The symbol only controls irq routing, not MSI-X. Signed-off-by: -
Avi Kivity authored
It is no longer possible to reproduce the problem any more, so presumably it has been fixed. Signed-off-by: -
Gleb Natapov authored
Since on vcpu entry we do it only if apic is enabled we should do it when TPR is changed while apic is disabled. This happens when windows resets HW without setting TPR to zero. Signed-off-by:
-
Joerg Roedel authored
Nested SVM is (in my experience) stable enough to be enabled by default. So omit the requirement to pass a module parameter. Signed-off-by:
Joerg Roedel <joerg.roedel@amd.com> Signed-off-by:
-
Joerg Roedel authored
Not checking for this flag breaks any nested hypervisor that does not set VINTR. So fix it with this patch. Signed-off-by:
-
Joerg Roedel authored
This patch removes one indentation level from nested_svm_intr and makes the logic more readable. Signed-off-by:
-
Joerg Roedel authored
This check is not necessary. We have to sync the vcpu->arch.cr2 always back to the VMCB. This patch remove the is_nested check. Signed-off-by:
-
Joerg Roedel authored
This patch moves the handling for special nested vmexits like #pf to a separate function. This makes the kvm_override parameter obsolete and makes the code more readable. Signed-off-by:
-
Joerg Roedel authored
If nested svm fails to load the msrpm the vmrun succeeds with the old msrpm which is not correct. This patch changes the logic to roll back to host mode in case the msrpm cannot be loaded. Signed-off-by:
-
Joerg Roedel authored
This function is not longer required. So remove it. Signed-off-by:
-
Joerg Roedel authored
This patch removes the usage of nested_svm_do from the vmrun emulation path. Signed-off-by:
-
Joerg Roedel authored
This patch removes the usage of nested_svm_do from the vmload and vmsave emulation code paths. Signed-off-by:
-
Joerg Roedel authored
This patch changes nested svm to call nested_svm_exit_handled_msr directly and not through nested_svm_do. [alex: fix oops due to nested kmap_atomics] Signed-off-by:
Alexander Graf <agraf@suse.de> Signed-off-by:
-
Joerg Roedel authored
This patch is the starting point of removing nested_svm_do from the nested svm code. The nested_svm_do function basically maps two guest physical pages to host virtual addresses and calls a passed function on it. This function pointer code flow is hard to read and not the best technical solution here. As a side effect this patch indroduces the nested_svm_[un]map helper functions. Signed-off-by:
-
Joerg Roedel authored
Makes the code of this function more readable by removing on indentation level for the core logic. Signed-off-by:
-
Joerg Roedel authored
If this function returns true a nested vmexit is required. Move that vmexit into the nested_svm_exit_handled function. This also simplifies the handling of nested #pf intercepts in this function. Signed-off-by:
-
Joerg Roedel authored
When caching guest intercepts there is no need anymore for the nested_svm_exit_handled_real function. So move its code into nested_svm_exit_handled. Signed-off-by:
-
Joerg Roedel authored
When the nested intercepts are cached we don't need to call get_user_pages and/or map the nested vmcb on every nested #vmexit to check who will handle the intercept. Further this patch aligns the emulated svm behavior better to real hardware. Signed-off-by:
-
Joerg Roedel authored
This makes it more clear for which purpose these members in the vcpu_svm exist. Signed-off-by:
-
Joerg Roedel authored
The interrupt completion code must run after nested exits are handled because not injected interrupts or exceptions may be handled by the l1 guest first. Signed-off-by:
-
