24 Oct, 2010
7 commits
-
Signed-off-by: Avi Kivity
-
This documents how to detect additional features inside the magic
page when a guest maps it.Signed-off-by: Alexander Graf
-
This adds some documentation for the KVM_INTERRUPT special cases that
PowerPC now implements.Signed-off-by: Alexander Graf
-
This is the guest side of the mtsr acceleration. Using this a guest can now
call mtsrin with almost no overhead as long as it ensures that it only uses
it with (MSR_IR|MSR_DR) == 0. Linux does that, so we're good.Signed-off-by: Alexander Graf
-
Basic informational document about x86 timekeeping and how KVM
is affected.Signed-off-by: Zachary Amsden
Signed-off-by: Marcelo Tosatti -
We need to tell the guest the opcodes that make up a hypercall through
interfaces that are controlled by userspace. So we need to add a call
for userspace to allow it to query those opcodes so it can pass them
on.This is required because the hypercall opcodes can change based on
the hypervisor conditions. If we're running in hardware accelerated
hypervisor mode, a hypercall looks different from when we're running
without hardware acceleration.Signed-off-by: Alexander Graf
Signed-off-by: Avi Kivity -
We just introduced a new PV interface that screams for documentation. So here
it is - a shiny new and awesome text file describing the internal works of
the PPC KVM paravirtual interface.Signed-off-by: Alexander Graf
Signed-off-by: Avi Kivity
02 Aug, 2010
2 commits
-
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti -
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti
01 Aug, 2010
12 commits
-
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti -
Equivalent (and better) functionality is provided by user-allocated memory
regions.Signed-off-by: Avi Kivity
-
As advertised in feature-removal-schedule.txt. Equivalent support is provided
by overlapping memory regions.Signed-off-by: Avi Kivity
-
Signed-off-by: Jason Wang
Signed-off-by: Marcelo Tosatti -
This patch enable save/restore of xsave state.
Signed-off-by: Sheng Yang
Signed-off-by: Marcelo Tosatti -
This patch adds a file that documents the usage of KVM-specific
MSRs.Signed-off-by: Glauber Costa
Reviewed-by: Randy Dunlap
Signed-off-by: Marcelo Tosatti -
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti -
Signed-off-by: Avi Kivity
-
When sp->role.direct is set, sp->gfns does not contain any essential
information, leaf sptes reachable from this sp are for a continuous
guest physical memory range (a linear range).
So sp->gfns[i] (if it was set) equals to sp->gfn + i. (PT_PAGE_TABLE_LEVEL)
Obviously, it is not essential information, we can calculate it when need.It means we don't need sp->gfns when sp->role.direct=1,
Thus we can save one page usage for every kvm_mmu_page.Note:
Access to sp->gfns must be wrapped by kvm_mmu_page_get_gfn()
or kvm_mmu_page_set_gfn().
It is only exposed in FNAME(sync_page).Signed-off-by: Lai Jiangshan
Signed-off-by: Avi Kivity -
There's no member "cr4_nxe" in struct kvm_mmu_page_role, it names "nxe" now.
Update mmu document.Signed-off-by: Gui Jianfeng
Signed-off-by: Marcelo Tosatti -
Signed-off-by: Avi Kivity
-
Signed-off-by: Avi Kivity
19 May, 2010
2 commits
-
When cr0.wp=0, we may shadow a gpte having u/s=1 and r/w=0 with an spte
having u/s=0 and r/w=1. This allows excessive access if the guest sets
cr0.wp=1 and accesses through this spte.Fix by making cr0.wp part of the base role; we'll have different sptes for
the two cases and the problem disappears.Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti -
This file documents cpuid bits used by KVM.
Signed-off-by: Glauber Costa
Acked-by: Zachary Amsden
Signed-off-by: Marcelo Tosatti
17 May, 2010
8 commits
-
Reported by Andrew Jones.
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti -
Acked-by: Pekka Enberg
Signed-off-by: Avi Kivity
Signed-off-by: Marcelo Tosatti -
Signed-off-by: Avi Kivity
-
Signed-off-by: Avi Kivity
-
MOL uses its own hypercall interface to call back into userspace when
the guest wants to do something.So let's implement that as an exit reason, specify it with a CAP and
only really use it when userspace wants us to.The only user of it so far is MOL.
Signed-off-by: Alexander Graf
Signed-off-by: Avi Kivity -
Some times we don't want all capabilities to be available to all
our vcpus. One example for that is the OSI interface, implemented
in the next patch.In order to have a generic mechanism in how to enable capabilities
individually, this patch introduces a new ioctl that can be used
for this purpose. That way features we don't want in all guests or
userspace configurations can just not be enabled and we're good.Signed-off-by: Alexander Graf
Signed-off-by: Avi Kivity -
Signed-off-by: Avi Kivity
-
Acked-by: Pekka Enberg
Signed-off-by: Avi Kivity
25 Apr, 2010
3 commits
-
So far user space was not able to save and restore debug registers for
migration or after reset. Plug this hole.Signed-off-by: Jan Kiszka
Signed-off-by: Avi Kivity -
The interrupt shadow created by STI or MOV-SS-like operations is part of
the VCPU state and must be preserved across migration. Transfer it in
the spare padding field of kvm_vcpu_events.interrupt.As a side effect we now have to make vmx_set_interrupt_shadow robust
against both shadow types being set. Give MOV SS a higher priority and
skip STI in that case to avoid that VMX throws a fault on next entry.Signed-off-by: Jan Kiszka
Signed-off-by: Avi Kivity -
Document that partially emulated instructions leave the guest state
inconsistent, and that the kernel will complete operations before
checking for pending signals.Signed-off-by: Marcelo Tosatti
Signed-off-by: Avi Kivity
01 Mar, 2010
1 commit
-
Signed-off-by: Wu Fengguang
Signed-off-by: Marcelo Tosatti
27 Dec, 2009
1 commit
-
User space may not want to overwrite asynchronously changing VCPU event
states on write-back. So allow to skip nmi.pending and sipi_vector by
setting corresponding bits in the flags field of kvm_vcpu_events.[avi: advertise the bits in KVM_GET_VCPU_EVENTS]
Signed-off-by: Jan Kiszka
Signed-off-by: Avi Kivity
03 Dec, 2009
3 commits
-
This new IOCTL exports all yet user-invisible states related to
exceptions, interrupts, and NMIs. Together with appropriate user space
changes, this fixes sporadic problems of vmsave/restore, live migration
and system reset.[avi: future-proof abi by adding a flags field]
Signed-off-by: Jan Kiszka
Signed-off-by: Avi Kivity -
When we migrate a kvm guest that uses pvclock between two hosts, we may
suffer a large skew. This is because there can be significant differences
between the monotonic clock of the hosts involved. When a new host with
a much larger monotonic time starts running the guest, the view of time
will be significantly impacted.Situation is much worse when we do the opposite, and migrate to a host with
a smaller monotonic clock.This proposed ioctl will allow userspace to inform us what is the monotonic
clock value in the source host, so we can keep the time skew short, and
more importantly, never goes backwards. Userspace may also need to trigger
the current data, since from the first migration onwards, it won't be
reflected by a simple call to clock_gettime() anymore.[marcelo: future-proof abi with a flags field]
[jan: fix KVM_GET_CLOCK by clearing flags field instead of checking it]Signed-off-by: Glauber Costa
Signed-off-by: Marcelo Tosatti
Signed-off-by: Avi Kivity -
Support for Xen PV-on-HVM guests can be implemented almost entirely in
userspace, except for handling one annoying MSR that maps a Xen
hypercall blob into guest address space.A generic mechanism to delegate MSR writes to userspace seems overkill
and risks encouraging similar MSR abuse in the future. Thus this patch
adds special support for the Xen HVM MSR.I implemented a new ioctl, KVM_XEN_HVM_CONFIG, that lets userspace tell
KVM which MSR the guest will write to, as well as the starting address
and size of the hypercall blobs (one each for 32-bit and 64-bit) that
userspace has loaded from files. When the guest writes to the MSR, KVM
copies one page of the blob from userspace to the guest.I've tested this patch with a hacked-up version of Gerd's userspace
code, booting a number of guests (CentOS 5.3 i386 and x86_64, and
FreeBSD 8.0-RC1 amd64) and exercising PV network and block devices.[jan: fix i386 build warning]
[avi: future proof abi with a flags field]Signed-off-by: Ed Swierk
Signed-off-by: Jan Kiszka
Signed-off-by: Marcelo Tosatti
Signed-off-by: Avi Kivity
10 Sep, 2009
1 commit
-
Signed-off-by: Avi Kivity