[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
#ifndef __LINUX_KVM_H
|
|
|
|
#define __LINUX_KVM_H
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Userspace interface for /dev/kvm - kernel based virtual machine
|
|
|
|
*
|
2007-07-17 07:12:26 -06:00
|
|
|
* Note: you must update KVM_API_VERSION if you change this interface.
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
*/
|
|
|
|
|
2009-01-15 14:51:26 -07:00
|
|
|
#include <linux/types.h>
|
2008-03-12 11:10:45 -06:00
|
|
|
#include <linux/compiler.h>
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
#include <linux/ioctl.h>
|
2007-11-19 16:06:31 -07:00
|
|
|
#include <asm/kvm.h>
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
|
2007-04-29 07:25:49 -06:00
|
|
|
#define KVM_API_VERSION 12
|
2006-12-22 02:06:02 -07:00
|
|
|
|
2009-11-02 09:20:28 -07:00
|
|
|
/* *** Deprecated interfaces *** */
|
|
|
|
|
|
|
|
#define KVM_TRC_SHIFT 16
|
|
|
|
|
|
|
|
#define KVM_TRC_ENTRYEXIT (1 << KVM_TRC_SHIFT)
|
|
|
|
#define KVM_TRC_HANDLER (1 << (KVM_TRC_SHIFT + 1))
|
|
|
|
|
|
|
|
#define KVM_TRC_VMENTRY (KVM_TRC_ENTRYEXIT + 0x01)
|
|
|
|
#define KVM_TRC_VMEXIT (KVM_TRC_ENTRYEXIT + 0x02)
|
|
|
|
#define KVM_TRC_PAGE_FAULT (KVM_TRC_HANDLER + 0x01)
|
|
|
|
|
|
|
|
#define KVM_TRC_HEAD_SIZE 12
|
|
|
|
#define KVM_TRC_CYCLE_SIZE 8
|
|
|
|
#define KVM_TRC_EXTRA_MAX 7
|
|
|
|
|
|
|
|
#define KVM_TRC_INJ_VIRQ (KVM_TRC_HANDLER + 0x02)
|
|
|
|
#define KVM_TRC_REDELIVER_EVT (KVM_TRC_HANDLER + 0x03)
|
|
|
|
#define KVM_TRC_PEND_INTR (KVM_TRC_HANDLER + 0x04)
|
|
|
|
#define KVM_TRC_IO_READ (KVM_TRC_HANDLER + 0x05)
|
|
|
|
#define KVM_TRC_IO_WRITE (KVM_TRC_HANDLER + 0x06)
|
|
|
|
#define KVM_TRC_CR_READ (KVM_TRC_HANDLER + 0x07)
|
|
|
|
#define KVM_TRC_CR_WRITE (KVM_TRC_HANDLER + 0x08)
|
|
|
|
#define KVM_TRC_DR_READ (KVM_TRC_HANDLER + 0x09)
|
|
|
|
#define KVM_TRC_DR_WRITE (KVM_TRC_HANDLER + 0x0A)
|
|
|
|
#define KVM_TRC_MSR_READ (KVM_TRC_HANDLER + 0x0B)
|
|
|
|
#define KVM_TRC_MSR_WRITE (KVM_TRC_HANDLER + 0x0C)
|
|
|
|
#define KVM_TRC_CPUID (KVM_TRC_HANDLER + 0x0D)
|
|
|
|
#define KVM_TRC_INTR (KVM_TRC_HANDLER + 0x0E)
|
|
|
|
#define KVM_TRC_NMI (KVM_TRC_HANDLER + 0x0F)
|
|
|
|
#define KVM_TRC_VMMCALL (KVM_TRC_HANDLER + 0x10)
|
|
|
|
#define KVM_TRC_HLT (KVM_TRC_HANDLER + 0x11)
|
|
|
|
#define KVM_TRC_CLTS (KVM_TRC_HANDLER + 0x12)
|
|
|
|
#define KVM_TRC_LMSW (KVM_TRC_HANDLER + 0x13)
|
|
|
|
#define KVM_TRC_APIC_ACCESS (KVM_TRC_HANDLER + 0x14)
|
|
|
|
#define KVM_TRC_TDP_FAULT (KVM_TRC_HANDLER + 0x15)
|
|
|
|
#define KVM_TRC_GTLB_WRITE (KVM_TRC_HANDLER + 0x16)
|
|
|
|
#define KVM_TRC_STLB_WRITE (KVM_TRC_HANDLER + 0x17)
|
|
|
|
#define KVM_TRC_STLB_INVAL (KVM_TRC_HANDLER + 0x18)
|
|
|
|
#define KVM_TRC_PPC_INSTR (KVM_TRC_HANDLER + 0x19)
|
|
|
|
|
2008-04-10 13:31:10 -06:00
|
|
|
struct kvm_user_trace_setup {
|
2009-11-02 09:20:28 -07:00
|
|
|
__u32 buf_size;
|
|
|
|
__u32 buf_nr;
|
|
|
|
};
|
|
|
|
|
|
|
|
#define __KVM_DEPRECATED_MAIN_W_0x06 \
|
|
|
|
_IOW(KVMIO, 0x06, struct kvm_user_trace_setup)
|
|
|
|
#define __KVM_DEPRECATED_MAIN_0x07 _IO(KVMIO, 0x07)
|
|
|
|
#define __KVM_DEPRECATED_MAIN_0x08 _IO(KVMIO, 0x08)
|
|
|
|
|
|
|
|
#define __KVM_DEPRECATED_VM_R_0x70 _IOR(KVMIO, 0x70, struct kvm_assigned_irq)
|
|
|
|
|
|
|
|
struct kvm_breakpoint {
|
|
|
|
__u32 enabled;
|
|
|
|
__u32 padding;
|
|
|
|
__u64 address;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct kvm_debug_guest {
|
|
|
|
__u32 enabled;
|
|
|
|
__u32 pad;
|
|
|
|
struct kvm_breakpoint breakpoints[4];
|
|
|
|
__u32 singlestep;
|
2008-04-10 13:31:10 -06:00
|
|
|
};
|
|
|
|
|
2009-11-02 09:20:28 -07:00
|
|
|
#define __KVM_DEPRECATED_VCPU_W_0x87 _IOW(KVMIO, 0x87, struct kvm_debug_guest)
|
|
|
|
|
|
|
|
/* *** End of deprecated interfaces *** */
|
|
|
|
|
|
|
|
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
/* for KVM_CREATE_MEMORY_REGION */
|
|
|
|
struct kvm_memory_region {
|
|
|
|
__u32 slot;
|
|
|
|
__u32 flags;
|
|
|
|
__u64 guest_phys_addr;
|
|
|
|
__u64 memory_size; /* bytes */
|
|
|
|
};
|
|
|
|
|
2007-10-09 11:20:39 -06:00
|
|
|
/* for KVM_SET_USER_MEMORY_REGION */
|
|
|
|
struct kvm_userspace_memory_region {
|
|
|
|
__u32 slot;
|
|
|
|
__u32 flags;
|
|
|
|
__u64 guest_phys_addr;
|
|
|
|
__u64 memory_size; /* bytes */
|
|
|
|
__u64 userspace_addr; /* start of the userspace allocated memory */
|
|
|
|
};
|
|
|
|
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
/* for kvm_memory_region::flags */
|
|
|
|
#define KVM_MEM_LOG_DIRTY_PAGES 1UL
|
|
|
|
|
|
|
|
|
2007-09-12 01:58:04 -06:00
|
|
|
/* for KVM_IRQ_LINE */
|
2007-07-06 03:20:49 -06:00
|
|
|
struct kvm_irq_level {
|
|
|
|
/*
|
|
|
|
* ACPI gsi notion of irq.
|
|
|
|
* For IA-64 (APIC model) IOAPIC0: irq 0-23; IOAPIC1: irq 24-47..
|
|
|
|
* For X86 (standard AT mode) PIC0/1: irq 0-15. IOAPIC0: 0-23..
|
|
|
|
*/
|
2009-02-04 08:28:14 -07:00
|
|
|
union {
|
|
|
|
__u32 irq;
|
|
|
|
__s32 status;
|
|
|
|
};
|
2007-07-06 03:20:49 -06:00
|
|
|
__u32 level;
|
|
|
|
};
|
|
|
|
|
2007-07-26 02:05:18 -06:00
|
|
|
|
|
|
|
struct kvm_irqchip {
|
|
|
|
__u32 chip_id;
|
|
|
|
__u32 pad;
|
|
|
|
union {
|
|
|
|
char dummy[512]; /* reserving space */
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_PIT
|
2007-07-26 02:05:18 -06:00
|
|
|
struct kvm_pic_state pic;
|
2007-12-17 05:27:27 -07:00
|
|
|
#endif
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_IOAPIC
|
2007-08-05 01:49:16 -06:00
|
|
|
struct kvm_ioapic_state ioapic;
|
2007-11-26 07:33:53 -07:00
|
|
|
#endif
|
2007-07-26 02:05:18 -06:00
|
|
|
} chip;
|
|
|
|
};
|
|
|
|
|
2009-05-14 14:42:53 -06:00
|
|
|
/* for KVM_CREATE_PIT2 */
|
|
|
|
struct kvm_pit_config {
|
|
|
|
__u32 flags;
|
|
|
|
__u32 pad[15];
|
|
|
|
};
|
|
|
|
|
|
|
|
#define KVM_PIT_SPEAKER_DUMMY 1
|
|
|
|
|
2007-10-10 06:03:16 -06:00
|
|
|
#define KVM_EXIT_UNKNOWN 0
|
|
|
|
#define KVM_EXIT_EXCEPTION 1
|
|
|
|
#define KVM_EXIT_IO 2
|
|
|
|
#define KVM_EXIT_HYPERCALL 3
|
|
|
|
#define KVM_EXIT_DEBUG 4
|
|
|
|
#define KVM_EXIT_HLT 5
|
|
|
|
#define KVM_EXIT_MMIO 6
|
|
|
|
#define KVM_EXIT_IRQ_WINDOW_OPEN 7
|
|
|
|
#define KVM_EXIT_SHUTDOWN 8
|
|
|
|
#define KVM_EXIT_FAIL_ENTRY 9
|
|
|
|
#define KVM_EXIT_INTR 10
|
|
|
|
#define KVM_EXIT_SET_TPR 11
|
2007-10-22 08:50:39 -06:00
|
|
|
#define KVM_EXIT_TPR_ACCESS 12
|
2008-03-25 11:47:23 -06:00
|
|
|
#define KVM_EXIT_S390_SIEIC 13
|
2008-03-25 11:47:34 -06:00
|
|
|
#define KVM_EXIT_S390_RESET 14
|
2008-04-16 22:28:07 -06:00
|
|
|
#define KVM_EXIT_DCR 15
|
2008-09-26 01:30:55 -06:00
|
|
|
#define KVM_EXIT_NMI 16
|
2009-06-11 06:43:28 -06:00
|
|
|
#define KVM_EXIT_INTERNAL_ERROR 17
|
|
|
|
|
|
|
|
/* For KVM_EXIT_INTERNAL_ERROR */
|
|
|
|
#define KVM_INTERNAL_ERROR_EMULATION 1
|
2009-11-04 02:59:01 -07:00
|
|
|
#define KVM_INTERNAL_ERROR_SIMUL_EX 2
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
|
2007-02-22 03:58:31 -07:00
|
|
|
/* for KVM_RUN, returned by mmap(vcpu_fd, offset=0) */
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
struct kvm_run {
|
|
|
|
/* in */
|
2007-01-05 17:36:24 -07:00
|
|
|
__u8 request_interrupt_window;
|
2008-12-11 08:54:54 -07:00
|
|
|
__u8 padding1[7];
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
|
|
|
|
/* out */
|
|
|
|
__u32 exit_reason;
|
2007-01-05 17:36:24 -07:00
|
|
|
__u8 ready_for_interrupt_injection;
|
|
|
|
__u8 if_flag;
|
2008-12-11 08:54:54 -07:00
|
|
|
__u8 padding2[2];
|
2007-02-12 01:54:39 -07:00
|
|
|
|
|
|
|
/* in (pre_kvm_run), out (post_kvm_run) */
|
2007-01-05 17:36:24 -07:00
|
|
|
__u64 cr8;
|
|
|
|
__u64 apic_base;
|
|
|
|
|
2009-11-19 06:21:16 -07:00
|
|
|
#ifdef __KVM_S390
|
|
|
|
/* the processor status word for s390 */
|
|
|
|
__u64 psw_mask; /* psw upper half */
|
|
|
|
__u64 psw_addr; /* psw lower half */
|
|
|
|
#endif
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
union {
|
|
|
|
/* KVM_EXIT_UNKNOWN */
|
|
|
|
struct {
|
2007-03-04 05:17:08 -07:00
|
|
|
__u64 hardware_exit_reason;
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
} hw;
|
2007-03-04 05:17:08 -07:00
|
|
|
/* KVM_EXIT_FAIL_ENTRY */
|
|
|
|
struct {
|
|
|
|
__u64 hardware_entry_failure_reason;
|
|
|
|
} fail_entry;
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
/* KVM_EXIT_EXCEPTION */
|
|
|
|
struct {
|
|
|
|
__u32 exception;
|
|
|
|
__u32 error_code;
|
|
|
|
} ex;
|
|
|
|
/* KVM_EXIT_IO */
|
2009-03-27 22:53:05 -06:00
|
|
|
struct {
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
#define KVM_EXIT_IO_IN 0
|
|
|
|
#define KVM_EXIT_IO_OUT 1
|
|
|
|
__u8 direction;
|
|
|
|
__u8 size; /* bytes */
|
|
|
|
__u16 port;
|
2007-03-20 04:46:50 -06:00
|
|
|
__u32 count;
|
|
|
|
__u64 data_offset; /* relative to kvm_run start */
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
} io;
|
|
|
|
struct {
|
2008-12-15 05:52:10 -07:00
|
|
|
struct kvm_debug_exit_arch arch;
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
} debug;
|
|
|
|
/* KVM_EXIT_MMIO */
|
|
|
|
struct {
|
|
|
|
__u64 phys_addr;
|
|
|
|
__u8 data[8];
|
|
|
|
__u32 len;
|
|
|
|
__u8 is_write;
|
|
|
|
} mmio;
|
2007-03-04 04:59:30 -07:00
|
|
|
/* KVM_EXIT_HYPERCALL */
|
|
|
|
struct {
|
2007-07-16 13:24:47 -06:00
|
|
|
__u64 nr;
|
2007-03-04 04:59:30 -07:00
|
|
|
__u64 args[6];
|
|
|
|
__u64 ret;
|
|
|
|
__u32 longmode;
|
|
|
|
__u32 pad;
|
|
|
|
} hypercall;
|
2007-10-22 08:50:39 -06:00
|
|
|
/* KVM_EXIT_TPR_ACCESS */
|
|
|
|
struct {
|
|
|
|
__u64 rip;
|
|
|
|
__u32 is_write;
|
|
|
|
__u32 pad;
|
|
|
|
} tpr_access;
|
2008-03-25 11:47:23 -06:00
|
|
|
/* KVM_EXIT_S390_SIEIC */
|
|
|
|
struct {
|
|
|
|
__u8 icptcode;
|
|
|
|
__u16 ipa;
|
|
|
|
__u32 ipb;
|
|
|
|
} s390_sieic;
|
2008-03-25 11:47:34 -06:00
|
|
|
/* KVM_EXIT_S390_RESET */
|
|
|
|
#define KVM_S390_RESET_POR 1
|
|
|
|
#define KVM_S390_RESET_CLEAR 2
|
|
|
|
#define KVM_S390_RESET_SUBSYSTEM 4
|
|
|
|
#define KVM_S390_RESET_CPU_INIT 8
|
|
|
|
#define KVM_S390_RESET_IPL 16
|
|
|
|
__u64 s390_reset_flags;
|
2008-04-16 22:28:07 -06:00
|
|
|
/* KVM_EXIT_DCR */
|
|
|
|
struct {
|
|
|
|
__u32 dcrn;
|
|
|
|
__u32 data;
|
|
|
|
__u8 is_write;
|
|
|
|
} dcr;
|
2009-06-11 06:43:28 -06:00
|
|
|
struct {
|
|
|
|
__u32 suberror;
|
2009-11-04 02:54:59 -07:00
|
|
|
/* Available with KVM_CAP_INTERNAL_ERROR_DATA: */
|
|
|
|
__u32 ndata;
|
|
|
|
__u64 data[16];
|
2009-06-11 06:43:28 -06:00
|
|
|
} internal;
|
2007-07-17 02:45:55 -06:00
|
|
|
/* Fix the size of the union. */
|
|
|
|
char padding[256];
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
};
|
|
|
|
};
|
|
|
|
|
2008-05-30 08:05:54 -06:00
|
|
|
/* for KVM_REGISTER_COALESCED_MMIO / KVM_UNREGISTER_COALESCED_MMIO */
|
|
|
|
|
|
|
|
struct kvm_coalesced_mmio_zone {
|
|
|
|
__u64 addr;
|
|
|
|
__u32 size;
|
|
|
|
__u32 pad;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct kvm_coalesced_mmio {
|
|
|
|
__u64 phys_addr;
|
|
|
|
__u32 len;
|
|
|
|
__u32 pad;
|
|
|
|
__u8 data[8];
|
|
|
|
};
|
|
|
|
|
|
|
|
struct kvm_coalesced_mmio_ring {
|
|
|
|
__u32 first, last;
|
|
|
|
struct kvm_coalesced_mmio coalesced_mmio[0];
|
|
|
|
};
|
|
|
|
|
|
|
|
#define KVM_COALESCED_MMIO_MAX \
|
|
|
|
((PAGE_SIZE - sizeof(struct kvm_coalesced_mmio_ring)) / \
|
|
|
|
sizeof(struct kvm_coalesced_mmio))
|
|
|
|
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
/* for KVM_TRANSLATE */
|
|
|
|
struct kvm_translation {
|
|
|
|
/* in */
|
|
|
|
__u64 linear_address;
|
|
|
|
|
|
|
|
/* out */
|
|
|
|
__u64 physical_address;
|
|
|
|
__u8 valid;
|
|
|
|
__u8 writeable;
|
|
|
|
__u8 usermode;
|
2007-02-12 01:54:41 -07:00
|
|
|
__u8 pad[5];
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
};
|
|
|
|
|
|
|
|
/* for KVM_INTERRUPT */
|
|
|
|
struct kvm_interrupt {
|
|
|
|
/* in */
|
|
|
|
__u32 irq;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* for KVM_GET_DIRTY_LOG */
|
|
|
|
struct kvm_dirty_log {
|
|
|
|
__u32 slot;
|
2009-03-27 22:53:05 -06:00
|
|
|
__u32 padding1;
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
union {
|
|
|
|
void __user *dirty_bitmap; /* one bit per page */
|
2009-03-27 22:53:05 -06:00
|
|
|
__u64 padding2;
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
};
|
|
|
|
};
|
|
|
|
|
2007-03-05 10:46:05 -07:00
|
|
|
/* for KVM_SET_SIGNAL_MASK */
|
|
|
|
struct kvm_signal_mask {
|
|
|
|
__u32 len;
|
|
|
|
__u8 sigset[0];
|
|
|
|
};
|
|
|
|
|
2007-10-22 08:50:39 -06:00
|
|
|
/* for KVM_TPR_ACCESS_REPORTING */
|
|
|
|
struct kvm_tpr_access_ctl {
|
|
|
|
__u32 enabled;
|
|
|
|
__u32 flags;
|
|
|
|
__u32 reserved[8];
|
|
|
|
};
|
|
|
|
|
2007-10-25 08:52:32 -06:00
|
|
|
/* for KVM_SET_VAPIC_ADDR */
|
|
|
|
struct kvm_vapic_addr {
|
|
|
|
__u64 vapic_addr;
|
|
|
|
};
|
|
|
|
|
2008-04-11 10:24:45 -06:00
|
|
|
/* for KVM_SET_MPSTATE */
|
|
|
|
|
|
|
|
#define KVM_MP_STATE_RUNNABLE 0
|
|
|
|
#define KVM_MP_STATE_UNINITIALIZED 1
|
|
|
|
#define KVM_MP_STATE_INIT_RECEIVED 2
|
|
|
|
#define KVM_MP_STATE_HALTED 3
|
|
|
|
#define KVM_MP_STATE_SIPI_RECEIVED 4
|
|
|
|
|
|
|
|
struct kvm_mp_state {
|
|
|
|
__u32 mp_state;
|
|
|
|
};
|
|
|
|
|
2008-03-25 11:47:20 -06:00
|
|
|
struct kvm_s390_psw {
|
|
|
|
__u64 mask;
|
|
|
|
__u64 addr;
|
|
|
|
};
|
|
|
|
|
KVM: s390: interrupt subsystem, cpu timer, waitpsw
This patch contains the s390 interrupt subsystem (similar to in kernel apic)
including timer interrupts (similar to in-kernel-pit) and enabled wait
(similar to in kernel hlt).
In order to achieve that, this patch also introduces intercept handling
for instruction intercepts, and it implements load control instructions.
This patch introduces an ioctl KVM_S390_INTERRUPT which is valid for both
the vm file descriptors and the vcpu file descriptors. In case this ioctl is
issued against a vm file descriptor, the interrupt is considered floating.
Floating interrupts may be delivered to any virtual cpu in the configuration.
The following interrupts are supported:
SIGP STOP - interprocessor signal that stops a remote cpu
SIGP SET PREFIX - interprocessor signal that sets the prefix register of a
(stopped) remote cpu
INT EMERGENCY - interprocessor interrupt, usually used to signal need_reshed
and for smp_call_function() in the guest.
PROGRAM INT - exception during program execution such as page fault, illegal
instruction and friends
RESTART - interprocessor signal that starts a stopped cpu
INT VIRTIO - floating interrupt for virtio signalisation
INT SERVICE - floating interrupt for signalisations from the system
service processor
struct kvm_s390_interrupt, which is submitted as ioctl parameter when injecting
an interrupt, also carrys parameter data for interrupts along with the interrupt
type. Interrupts on s390 usually have a state that represents the current
operation, or identifies which device has caused the interruption on s390.
kvm_s390_handle_wait() does handle waitpsw in two flavors: in case of a
disabled wait (that is, disabled for interrupts), we exit to userspace. In case
of an enabled wait we set up a timer that equals the cpu clock comparator value
and sleep on a wait queue.
[christian: change virtio interrupt to 0x2603]
Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Carsten Otte <cotte@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
2008-03-25 11:47:26 -06:00
|
|
|
/* valid values for type in kvm_s390_interrupt */
|
|
|
|
#define KVM_S390_SIGP_STOP 0xfffe0000u
|
|
|
|
#define KVM_S390_PROGRAM_INT 0xfffe0001u
|
|
|
|
#define KVM_S390_SIGP_SET_PREFIX 0xfffe0002u
|
|
|
|
#define KVM_S390_RESTART 0xfffe0003u
|
|
|
|
#define KVM_S390_INT_VIRTIO 0xffff2603u
|
|
|
|
#define KVM_S390_INT_SERVICE 0xffff2401u
|
|
|
|
#define KVM_S390_INT_EMERGENCY 0xffff1201u
|
|
|
|
|
|
|
|
struct kvm_s390_interrupt {
|
|
|
|
__u32 type;
|
|
|
|
__u32 parm;
|
|
|
|
__u64 parm64;
|
|
|
|
};
|
|
|
|
|
2008-12-15 05:52:10 -07:00
|
|
|
/* for KVM_SET_GUEST_DEBUG */
|
|
|
|
|
|
|
|
#define KVM_GUESTDBG_ENABLE 0x00000001
|
|
|
|
#define KVM_GUESTDBG_SINGLESTEP 0x00000002
|
|
|
|
|
|
|
|
struct kvm_guest_debug {
|
|
|
|
__u32 control;
|
|
|
|
__u32 pad;
|
|
|
|
struct kvm_guest_debug_arch arch;
|
|
|
|
};
|
|
|
|
|
KVM: add ioeventfd support
ioeventfd is a mechanism to register PIO/MMIO regions to trigger an eventfd
signal when written to by a guest. Host userspace can register any
arbitrary IO address with a corresponding eventfd and then pass the eventfd
to a specific end-point of interest for handling.
Normal IO requires a blocking round-trip since the operation may cause
side-effects in the emulated model or may return data to the caller.
Therefore, an IO in KVM traps from the guest to the host, causes a VMX/SVM
"heavy-weight" exit back to userspace, and is ultimately serviced by qemu's
device model synchronously before returning control back to the vcpu.
However, there is a subclass of IO which acts purely as a trigger for
other IO (such as to kick off an out-of-band DMA request, etc). For these
patterns, the synchronous call is particularly expensive since we really
only want to simply get our notification transmitted asychronously and
return as quickly as possible. All the sychronous infrastructure to ensure
proper data-dependencies are met in the normal IO case are just unecessary
overhead for signalling. This adds additional computational load on the
system, as well as latency to the signalling path.
Therefore, we provide a mechanism for registration of an in-kernel trigger
point that allows the VCPU to only require a very brief, lightweight
exit just long enough to signal an eventfd. This also means that any
clients compatible with the eventfd interface (which includes userspace
and kernelspace equally well) can now register to be notified. The end
result should be a more flexible and higher performance notification API
for the backend KVM hypervisor and perhipheral components.
To test this theory, we built a test-harness called "doorbell". This
module has a function called "doorbell_ring()" which simply increments a
counter for each time the doorbell is signaled. It supports signalling
from either an eventfd, or an ioctl().
We then wired up two paths to the doorbell: One via QEMU via a registered
io region and through the doorbell ioctl(). The other is direct via
ioeventfd.
You can download this test harness here:
ftp://ftp.novell.com/dev/ghaskins/doorbell.tar.bz2
The measured results are as follows:
qemu-mmio: 110000 iops, 9.09us rtt
ioeventfd-mmio: 200100 iops, 5.00us rtt
ioeventfd-pio: 367300 iops, 2.72us rtt
I didn't measure qemu-pio, because I have to figure out how to register a
PIO region with qemu's device model, and I got lazy. However, for now we
can extrapolate based on the data from the NULLIO runs of +2.56us for MMIO,
and -350ns for HC, we get:
qemu-pio: 153139 iops, 6.53us rtt
ioeventfd-hc: 412585 iops, 2.37us rtt
these are just for fun, for now, until I can gather more data.
Here is a graph for your convenience:
http://developer.novell.com/wiki/images/7/76/Iofd-chart.png
The conclusion to draw is that we save about 4us by skipping the userspace
hop.
--------------------
Signed-off-by: Gregory Haskins <ghaskins@novell.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
2009-07-07 15:08:49 -06:00
|
|
|
enum {
|
|
|
|
kvm_ioeventfd_flag_nr_datamatch,
|
|
|
|
kvm_ioeventfd_flag_nr_pio,
|
|
|
|
kvm_ioeventfd_flag_nr_deassign,
|
|
|
|
kvm_ioeventfd_flag_nr_max,
|
|
|
|
};
|
|
|
|
|
|
|
|
#define KVM_IOEVENTFD_FLAG_DATAMATCH (1 << kvm_ioeventfd_flag_nr_datamatch)
|
|
|
|
#define KVM_IOEVENTFD_FLAG_PIO (1 << kvm_ioeventfd_flag_nr_pio)
|
|
|
|
#define KVM_IOEVENTFD_FLAG_DEASSIGN (1 << kvm_ioeventfd_flag_nr_deassign)
|
|
|
|
|
|
|
|
#define KVM_IOEVENTFD_VALID_FLAG_MASK ((1 << kvm_ioeventfd_flag_nr_max) - 1)
|
|
|
|
|
|
|
|
struct kvm_ioeventfd {
|
|
|
|
__u64 datamatch;
|
|
|
|
__u64 addr; /* legal pio/mmio address */
|
|
|
|
__u32 len; /* 1, 2, 4, or 8 bytes */
|
|
|
|
__s32 fd;
|
|
|
|
__u32 flags;
|
|
|
|
__u8 pad[36];
|
|
|
|
};
|
|
|
|
|
[PATCH] kvm: userspace interface
web site: http://kvm.sourceforge.net
mailing list: kvm-devel@lists.sourceforge.net
(http://lists.sourceforge.net/lists/listinfo/kvm-devel)
The following patchset adds a driver for Intel's hardware virtualization
extensions to the x86 architecture. The driver adds a character device
(/dev/kvm) that exposes the virtualization capabilities to userspace. Using
this driver, a process can run a virtual machine (a "guest") in a fully
virtualized PC containing its own virtual hard disks, network adapters, and
display.
Using this driver, one can start multiple virtual machines on a host.
Each virtual machine is a process on the host; a virtual cpu is a thread in
that process. kill(1), nice(1), top(1) work as expected. In effect, the
driver adds a third execution mode to the existing two: we now have kernel
mode, user mode, and guest mode. Guest mode has its own address space mapping
guest physical memory (which is accessible to user mode by mmap()ing
/dev/kvm). Guest mode has no access to any I/O devices; any such access is
intercepted and directed to user mode for emulation.
The driver supports i386 and x86_64 hosts and guests. All combinations are
allowed except x86_64 guest on i386 host. For i386 guests and hosts, both pae
and non-pae paging modes are supported.
SMP hosts and UP guests are supported. At the moment only Intel
hardware is supported, but AMD virtualization support is being worked on.
Performance currently is non-stellar due to the naive implementation of the
mmu virtualization, which throws away most of the shadow page table entries
every context switch. We plan to address this in two ways:
- cache shadow page tables across tlb flushes
- wait until AMD and Intel release processors with nested page tables
Currently a virtual desktop is responsive but consumes a lot of CPU. Under
Windows I tried playing pinball and watching a few flash movies; with a recent
CPU one can hardly feel the virtualization. Linux/X is slower, probably due
to X being in a separate process.
In addition to the driver, you need a slightly modified qemu to provide I/O
device emulation and the BIOS.
Caveats (akpm: might no longer be true):
- The Windows install currently bluescreens due to a problem with the
virtual APIC. We are working on a fix. A temporary workaround is to
use an existing image or install through qemu
- Windows 64-bit does not work. That's also true for qemu, so it's
probably a problem with the device model.
[bero@arklinux.org: build fix]
[simon.kagstrom@bth.se: build fix, other fixes]
[uril@qumranet.com: KVM: Expose interrupt bitmap]
[akpm@osdl.org: i386 build fix]
[mingo@elte.hu: i386 fixes]
[rdreier@cisco.com: add log levels to all printks]
[randy.dunlap@oracle.com: Fix sparse NULL and C99 struct init warnings]
[anthony@codemonkey.ws: KVM: AMD SVM: 32-bit host support]
Signed-off-by: Yaniv Kamay <yaniv@qumranet.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
Cc: Simon Kagstrom <simon.kagstrom@bth.se>
Cc: Bernhard Rosenkraenzer <bero@arklinux.org>
Signed-off-by: Uri Lublin <uril@qumranet.com>
Cc: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rolandd@cisco.com>
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Anthony Liguori <anthony@codemonkey.ws>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-12-10 03:21:36 -07:00
|
|
|
#define KVMIO 0xAE
|
|
|
|
|
2007-02-21 10:28:04 -07:00
|
|
|
/*
|
|
|
|
* ioctls for /dev/kvm fds:
|
|
|
|
*/
|
2007-03-01 08:20:13 -07:00
|
|
|
#define KVM_GET_API_VERSION _IO(KVMIO, 0x00)
|
|
|
|
#define KVM_CREATE_VM _IO(KVMIO, 0x01) /* returns a VM fd */
|
|
|
|
#define KVM_GET_MSR_INDEX_LIST _IOWR(KVMIO, 0x02, struct kvm_msr_list)
|
2008-03-25 11:47:20 -06:00
|
|
|
|
|
|
|
#define KVM_S390_ENABLE_SIE _IO(KVMIO, 0x06)
|
2007-03-01 08:56:20 -07:00
|
|
|
/*
|
|
|
|
* Check if a kvm extension is available. Argument is extension number,
|
|
|
|
* return is 1 (yes) or 0 (no, sorry).
|
|
|
|
*/
|
|
|
|
#define KVM_CHECK_EXTENSION _IO(KVMIO, 0x03)
|
2007-03-07 04:05:38 -07:00
|
|
|
/*
|
|
|
|
* Get size for mmap(vcpu_fd)
|
|
|
|
*/
|
|
|
|
#define KVM_GET_VCPU_MMAP_SIZE _IO(KVMIO, 0x04) /* in bytes */
|
2008-02-11 09:37:23 -07:00
|
|
|
#define KVM_GET_SUPPORTED_CPUID _IOWR(KVMIO, 0x05, struct kvm_cpuid2)
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_TRACE_ENABLE __KVM_DEPRECATED_MAIN_W_0x06
|
|
|
|
#define KVM_TRACE_PAUSE __KVM_DEPRECATED_MAIN_0x07
|
|
|
|
#define KVM_TRACE_DISABLE __KVM_DEPRECATED_MAIN_0x08
|
|
|
|
|
2007-07-06 03:20:49 -06:00
|
|
|
/*
|
|
|
|
* Extension capability list.
|
|
|
|
*/
|
|
|
|
#define KVM_CAP_IRQCHIP 0
|
2007-07-18 03:15:21 -06:00
|
|
|
#define KVM_CAP_HLT 1
|
2007-10-02 10:52:55 -06:00
|
|
|
#define KVM_CAP_MMU_SHADOW_CACHE_CONTROL 2
|
2007-10-09 11:20:39 -06:00
|
|
|
#define KVM_CAP_USER_MEMORY 3
|
2007-10-24 16:29:55 -06:00
|
|
|
#define KVM_CAP_SET_TSS_ADDR 4
|
2007-10-22 08:50:39 -06:00
|
|
|
#define KVM_CAP_VAPIC 6
|
2008-02-11 09:37:23 -07:00
|
|
|
#define KVM_CAP_EXT_CPUID 7
|
2008-02-15 12:52:47 -07:00
|
|
|
#define KVM_CAP_CLOCKSOURCE 8
|
2008-02-20 02:53:16 -07:00
|
|
|
#define KVM_CAP_NR_VCPUS 9 /* returns max vcpus per vm */
|
2008-02-20 02:59:20 -07:00
|
|
|
#define KVM_CAP_NR_MEMSLOTS 10 /* returns max memory slots per vm */
|
2008-01-27 14:10:22 -07:00
|
|
|
#define KVM_CAP_PIT 11
|
2008-02-22 10:21:36 -07:00
|
|
|
#define KVM_CAP_NOP_IO_DELAY 12
|
2008-02-22 10:21:37 -07:00
|
|
|
#define KVM_CAP_PV_MMU 13
|
2008-04-11 10:24:45 -06:00
|
|
|
#define KVM_CAP_MP_STATE 14
|
2008-05-30 08:05:54 -06:00
|
|
|
#define KVM_CAP_COALESCED_MMIO 15
|
2008-07-29 02:30:57 -06:00
|
|
|
#define KVM_CAP_SYNC_MMU 16 /* Changes to host mmap are reflected in guest */
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_DEVICE_ASSIGNMENT
|
2008-07-28 10:26:26 -06:00
|
|
|
#define KVM_CAP_DEVICE_ASSIGNMENT 17
|
2008-10-05 23:47:38 -06:00
|
|
|
#endif
|
2008-09-13 18:48:28 -06:00
|
|
|
#define KVM_CAP_IOMMU 18
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_MSI
|
2008-11-23 23:32:56 -07:00
|
|
|
#define KVM_CAP_DEVICE_MSI 20
|
|
|
|
#endif
|
2008-12-08 09:25:27 -07:00
|
|
|
/* Bug in KVM_SET_USER_MEMORY_REGION fixed: */
|
|
|
|
#define KVM_CAP_DESTROY_MEMORY_REGION_WORKS 21
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_USER_NMI
|
2008-12-11 08:54:54 -07:00
|
|
|
#define KVM_CAP_USER_NMI 22
|
|
|
|
#endif
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_GUEST_DEBUG
|
2008-12-15 05:52:10 -07:00
|
|
|
#define KVM_CAP_SET_GUEST_DEBUG 23
|
2008-12-19 10:13:54 -07:00
|
|
|
#endif
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_PIT
|
2008-12-30 10:55:06 -07:00
|
|
|
#define KVM_CAP_REINJECT_CONTROL 24
|
2008-11-19 04:58:46 -07:00
|
|
|
#endif
|
2009-01-19 05:57:52 -07:00
|
|
|
#ifdef __KVM_HAVE_IOAPIC
|
2008-11-19 04:58:46 -07:00
|
|
|
#define KVM_CAP_IRQ_ROUTING 25
|
|
|
|
#endif
|
2009-02-04 08:28:14 -07:00
|
|
|
#define KVM_CAP_IRQ_INJECT_STATUS 26
|
2009-02-12 19:50:56 -07:00
|
|
|
#ifdef __KVM_HAVE_DEVICE_ASSIGNMENT
|
|
|
|
#define KVM_CAP_DEVICE_DEASSIGNMENT 27
|
|
|
|
#endif
|
KVM: Enable MSI-X for KVM assigned device
This patch finally enable MSI-X.
What we need for MSI-X:
1. Intercept one page in MMIO region of device. So that we can get guest desired
MSI-X table and set up the real one. Now this have been done by guest, and
transfer to kernel using ioctl KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY.
2. Information for incoming interrupt. Now one device can have more than one
interrupt, and they are all handled by one workqueue structure. So we need to
identify them. The previous patch enable gsi_msg_pending_bitmap get this done.
3. Mapping from host IRQ to guest gsi as well as guest gsi to real MSI/MSI-X
message address/data. We used same entry number for the host and guest here, so
that it's easy to find the correlated guest gsi.
What we lack for now:
1. The PCI spec said nothing can existed with MSI-X table in the same page of
MMIO region, except pending bits. The patch ignore pending bits as the first
step (so they are always 0 - no pending).
2. The PCI spec allowed to change MSI-X table dynamically. That means, the OS
can enable MSI-X, then mask one MSI-X entry, modify it, and unmask it. The patch
didn't support this, and Linux also don't work in this way.
3. The patch didn't implement MSI-X mask all and mask single entry. I would
implement the former in driver/pci/msi.c later. And for single entry, userspace
should have reposibility to handle it.
Signed-off-by: Sheng Yang <sheng@linux.intel.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
2009-02-25 02:22:28 -07:00
|
|
|
#ifdef __KVM_HAVE_MSIX
|
|
|
|
#define KVM_CAP_DEVICE_MSIX 28
|
|
|
|
#endif
|
2009-03-12 07:45:39 -06:00
|
|
|
#define KVM_CAP_ASSIGN_DEV_IRQ 29
|
2009-04-13 03:59:32 -06:00
|
|
|
/* Another bug in KVM_SET_USER_MEMORY_REGION fixed: */
|
|
|
|
#define KVM_CAP_JOIN_MEMORY_REGIONS_WORKS 30
|
2009-05-11 02:48:15 -06:00
|
|
|
#ifdef __KVM_HAVE_MCE
|
|
|
|
#define KVM_CAP_MCE 31
|
|
|
|
#endif
|
2009-05-20 08:30:49 -06:00
|
|
|
#define KVM_CAP_IRQFD 32
|
2009-05-14 14:42:53 -06:00
|
|
|
#ifdef __KVM_HAVE_PIT
|
|
|
|
#define KVM_CAP_PIT2 33
|
|
|
|
#endif
|
2009-06-09 06:56:28 -06:00
|
|
|
#define KVM_CAP_SET_BOOT_CPU_ID 34
|
2009-07-07 09:50:38 -06:00
|
|
|
#ifdef __KVM_HAVE_PIT_STATE2
|
|
|
|
#define KVM_CAP_PIT_STATE2 35
|
|
|
|
#endif
|
KVM: add ioeventfd support
ioeventfd is a mechanism to register PIO/MMIO regions to trigger an eventfd
signal when written to by a guest. Host userspace can register any
arbitrary IO address with a corresponding eventfd and then pass the eventfd
to a specific end-point of interest for handling.
Normal IO requires a blocking round-trip since the operation may cause
side-effects in the emulated model or may return data to the caller.
Therefore, an IO in KVM traps from the guest to the host, causes a VMX/SVM
"heavy-weight" exit back to userspace, and is ultimately serviced by qemu's
device model synchronously before returning control back to the vcpu.
However, there is a subclass of IO which acts purely as a trigger for
other IO (such as to kick off an out-of-band DMA request, etc). For these
patterns, the synchronous call is particularly expensive since we really
only want to simply get our notification transmitted asychronously and
return as quickly as possible. All the sychronous infrastructure to ensure
proper data-dependencies are met in the normal IO case are just unecessary
overhead for signalling. This adds additional computational load on the
system, as well as latency to the signalling path.
Therefore, we provide a mechanism for registration of an in-kernel trigger
point that allows the VCPU to only require a very brief, lightweight
exit just long enough to signal an eventfd. This also means that any
clients compatible with the eventfd interface (which includes userspace
and kernelspace equally well) can now register to be notified. The end
result should be a more flexible and higher performance notification API
for the backend KVM hypervisor and perhipheral components.
To test this theory, we built a test-harness called "doorbell". This
module has a function called "doorbell_ring()" which simply increments a
counter for each time the doorbell is signaled. It supports signalling
from either an eventfd, or an ioctl().
We then wired up two paths to the doorbell: One via QEMU via a registered
io region and through the doorbell ioctl(). The other is direct via
ioeventfd.
You can download this test harness here:
ftp://ftp.novell.com/dev/ghaskins/doorbell.tar.bz2
The measured results are as follows:
qemu-mmio: 110000 iops, 9.09us rtt
ioeventfd-mmio: 200100 iops, 5.00us rtt
ioeventfd-pio: 367300 iops, 2.72us rtt
I didn't measure qemu-pio, because I have to figure out how to register a
PIO region with qemu's device model, and I got lazy. However, for now we
can extrapolate based on the data from the NULLIO runs of +2.56us for MMIO,
and -350ns for HC, we get:
qemu-pio: 153139 iops, 6.53us rtt
ioeventfd-hc: 412585 iops, 2.37us rtt
these are just for fun, for now, until I can gather more data.
Here is a graph for your convenience:
http://developer.novell.com/wiki/images/7/76/Iofd-chart.png
The conclusion to draw is that we save about 4us by skipping the userspace
hop.
--------------------
Signed-off-by: Gregory Haskins <ghaskins@novell.com>
Acked-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
2009-07-07 15:08:49 -06:00
|
|
|
#define KVM_CAP_IOEVENTFD 36
|
2009-07-20 20:42:48 -06:00
|
|
|
#define KVM_CAP_SET_IDENTITY_MAP_ADDR 37
|
2009-10-15 16:21:43 -06:00
|
|
|
#ifdef __KVM_HAVE_XEN_HVM
|
|
|
|
#define KVM_CAP_XEN_HVM 38
|
|
|
|
#endif
|
2009-10-16 13:28:36 -06:00
|
|
|
#define KVM_CAP_ADJUST_CLOCK 39
|
2009-11-04 02:54:59 -07:00
|
|
|
#define KVM_CAP_INTERNAL_ERROR_DATA 40
|
2009-11-11 17:04:25 -07:00
|
|
|
#ifdef __KVM_HAVE_VCPU_EVENTS
|
|
|
|
#define KVM_CAP_VCPU_EVENTS 41
|
|
|
|
#endif
|
2009-11-19 06:21:16 -07:00
|
|
|
#define KVM_CAP_S390_PSW 42
|
2009-11-29 20:02:02 -07:00
|
|
|
#define KVM_CAP_PPC_SEGSTATE 43
|
2008-11-19 04:58:46 -07:00
|
|
|
|
|
|
|
#ifdef KVM_CAP_IRQ_ROUTING
|
|
|
|
|
|
|
|
struct kvm_irq_routing_irqchip {
|
|
|
|
__u32 irqchip;
|
|
|
|
__u32 pin;
|
|
|
|
};
|
|
|
|
|
2009-02-09 22:57:06 -07:00
|
|
|
struct kvm_irq_routing_msi {
|
|
|
|
__u32 address_lo;
|
|
|
|
__u32 address_hi;
|
|
|
|
__u32 data;
|
|
|
|
__u32 pad;
|
|
|
|
};
|
|
|
|
|
2008-11-19 04:58:46 -07:00
|
|
|
/* gsi routing entry types */
|
|
|
|
#define KVM_IRQ_ROUTING_IRQCHIP 1
|
2009-02-09 22:57:06 -07:00
|
|
|
#define KVM_IRQ_ROUTING_MSI 2
|
2008-11-19 04:58:46 -07:00
|
|
|
|
|
|
|
struct kvm_irq_routing_entry {
|
|
|
|
__u32 gsi;
|
|
|
|
__u32 type;
|
|
|
|
__u32 flags;
|
|
|
|
__u32 pad;
|
|
|
|
union {
|
|
|
|
struct kvm_irq_routing_irqchip irqchip;
|
2009-02-09 22:57:06 -07:00
|
|
|
struct kvm_irq_routing_msi msi;
|
2008-11-19 04:58:46 -07:00
|
|
|
__u32 pad[8];
|
|
|
|
} u;
|
|
|
|
};
|
|
|
|
|
|
|
|
struct kvm_irq_routing {
|
|
|
|
__u32 nr;
|
|
|
|
__u32 flags;
|
|
|
|
struct kvm_irq_routing_entry entries[0];
|
|
|
|
};
|
|
|
|
|
2008-12-30 10:55:06 -07:00
|
|
|
#endif
|
2007-07-06 03:20:49 -06:00
|
|
|
|
2009-05-11 02:48:15 -06:00
|
|
|
#ifdef KVM_CAP_MCE
|
|
|
|
/* x86 MCE */
|
|
|
|
struct kvm_x86_mce {
|
|
|
|
__u64 status;
|
|
|
|
__u64 addr;
|
|
|
|
__u64 misc;
|
|
|
|
__u64 mcg_status;
|
|
|
|
__u8 bank;
|
|
|
|
__u8 pad1[7];
|
|
|
|
__u64 pad2[3];
|
|
|
|
};
|
|
|
|
#endif
|
|
|
|
|
2009-10-15 16:21:43 -06:00
|
|
|
#ifdef KVM_CAP_XEN_HVM
|
|
|
|
struct kvm_xen_hvm_config {
|
|
|
|
__u32 flags;
|
|
|
|
__u32 msr;
|
|
|
|
__u64 blob_addr_32;
|
|
|
|
__u64 blob_addr_64;
|
|
|
|
__u8 blob_size_32;
|
|
|
|
__u8 blob_size_64;
|
|
|
|
__u8 pad2[30];
|
|
|
|
};
|
|
|
|
#endif
|
|
|
|
|
2009-05-20 08:30:49 -06:00
|
|
|
#define KVM_IRQFD_FLAG_DEASSIGN (1 << 0)
|
|
|
|
|
|
|
|
struct kvm_irqfd {
|
|
|
|
__u32 fd;
|
|
|
|
__u32 gsi;
|
|
|
|
__u32 flags;
|
|
|
|
__u8 pad[20];
|
|
|
|
};
|
|
|
|
|
2009-10-16 13:28:36 -06:00
|
|
|
struct kvm_clock_data {
|
|
|
|
__u64 clock;
|
|
|
|
__u32 flags;
|
|
|
|
__u32 pad[9];
|
|
|
|
};
|
|
|
|
|
2007-02-21 10:28:04 -07:00
|
|
|
/*
|
|
|
|
* ioctls for VM fds
|
|
|
|
*/
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_SET_MEMORY_REGION _IOW(KVMIO, 0x40, struct kvm_memory_region)
|
2007-02-21 09:04:26 -07:00
|
|
|
/*
|
|
|
|
* KVM_CREATE_VCPU receives as a parameter the vcpu slot, and returns
|
|
|
|
* a vcpu fd.
|
|
|
|
*/
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_CREATE_VCPU _IO(KVMIO, 0x41)
|
|
|
|
#define KVM_GET_DIRTY_LOG _IOW(KVMIO, 0x42, struct kvm_dirty_log)
|
|
|
|
#define KVM_SET_MEMORY_ALIAS _IOW(KVMIO, 0x43, struct kvm_memory_alias)
|
|
|
|
#define KVM_SET_NR_MMU_PAGES _IO(KVMIO, 0x44)
|
|
|
|
#define KVM_GET_NR_MMU_PAGES _IO(KVMIO, 0x45)
|
|
|
|
#define KVM_SET_USER_MEMORY_REGION _IOW(KVMIO, 0x46, \
|
2009-06-09 02:33:36 -06:00
|
|
|
struct kvm_userspace_memory_region)
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_SET_TSS_ADDR _IO(KVMIO, 0x47)
|
|
|
|
#define KVM_SET_IDENTITY_MAP_ADDR _IOW(KVMIO, 0x48, __u64)
|
2007-07-06 03:20:49 -06:00
|
|
|
/* Device model IOC */
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_CREATE_IRQCHIP _IO(KVMIO, 0x60)
|
|
|
|
#define KVM_IRQ_LINE _IOW(KVMIO, 0x61, struct kvm_irq_level)
|
|
|
|
#define KVM_GET_IRQCHIP _IOWR(KVMIO, 0x62, struct kvm_irqchip)
|
|
|
|
#define KVM_SET_IRQCHIP _IOR(KVMIO, 0x63, struct kvm_irqchip)
|
|
|
|
#define KVM_CREATE_PIT _IO(KVMIO, 0x64)
|
|
|
|
#define KVM_GET_PIT _IOWR(KVMIO, 0x65, struct kvm_pit_state)
|
|
|
|
#define KVM_SET_PIT _IOR(KVMIO, 0x66, struct kvm_pit_state)
|
|
|
|
#define KVM_IRQ_LINE_STATUS _IOWR(KVMIO, 0x67, struct kvm_irq_level)
|
2008-05-30 08:05:54 -06:00
|
|
|
#define KVM_REGISTER_COALESCED_MMIO \
|
|
|
|
_IOW(KVMIO, 0x67, struct kvm_coalesced_mmio_zone)
|
|
|
|
#define KVM_UNREGISTER_COALESCED_MMIO \
|
|
|
|
_IOW(KVMIO, 0x68, struct kvm_coalesced_mmio_zone)
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_ASSIGN_PCI_DEVICE _IOR(KVMIO, 0x69, \
|
|
|
|
struct kvm_assigned_pci_dev)
|
|
|
|
#define KVM_SET_GSI_ROUTING _IOW(KVMIO, 0x6a, struct kvm_irq_routing)
|
2009-03-12 07:45:39 -06:00
|
|
|
/* deprecated, replaced by KVM_ASSIGN_DEV_IRQ */
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_ASSIGN_IRQ __KVM_DEPRECATED_VM_R_0x70
|
|
|
|
#define KVM_ASSIGN_DEV_IRQ _IOW(KVMIO, 0x70, struct kvm_assigned_irq)
|
|
|
|
#define KVM_REINJECT_CONTROL _IO(KVMIO, 0x71)
|
|
|
|
#define KVM_DEASSIGN_PCI_DEVICE _IOW(KVMIO, 0x72, \
|
|
|
|
struct kvm_assigned_pci_dev)
|
|
|
|
#define KVM_ASSIGN_SET_MSIX_NR _IOW(KVMIO, 0x73, \
|
|
|
|
struct kvm_assigned_msix_nr)
|
|
|
|
#define KVM_ASSIGN_SET_MSIX_ENTRY _IOW(KVMIO, 0x74, \
|
|
|
|
struct kvm_assigned_msix_entry)
|
|
|
|
#define KVM_DEASSIGN_DEV_IRQ _IOW(KVMIO, 0x75, struct kvm_assigned_irq)
|
|
|
|
#define KVM_IRQFD _IOW(KVMIO, 0x76, struct kvm_irqfd)
|
|
|
|
#define KVM_CREATE_PIT2 _IOW(KVMIO, 0x77, struct kvm_pit_config)
|
|
|
|
#define KVM_SET_BOOT_CPU_ID _IO(KVMIO, 0x78)
|
|
|
|
#define KVM_IOEVENTFD _IOW(KVMIO, 0x79, struct kvm_ioeventfd)
|
|
|
|
#define KVM_XEN_HVM_CONFIG _IOW(KVMIO, 0x7a, struct kvm_xen_hvm_config)
|
|
|
|
#define KVM_SET_CLOCK _IOW(KVMIO, 0x7b, struct kvm_clock_data)
|
|
|
|
#define KVM_GET_CLOCK _IOR(KVMIO, 0x7c, struct kvm_clock_data)
|
|
|
|
/* Available with KVM_CAP_PIT_STATE2 */
|
|
|
|
#define KVM_GET_PIT2 _IOR(KVMIO, 0x9f, struct kvm_pit_state2)
|
|
|
|
#define KVM_SET_PIT2 _IOW(KVMIO, 0xa0, struct kvm_pit_state2)
|
2007-02-21 09:04:26 -07:00
|
|
|
|
|
|
|
/*
|
|
|
|
* ioctls for vcpu fds
|
|
|
|
*/
|
2007-03-01 08:20:13 -07:00
|
|
|
#define KVM_RUN _IO(KVMIO, 0x80)
|
|
|
|
#define KVM_GET_REGS _IOR(KVMIO, 0x81, struct kvm_regs)
|
|
|
|
#define KVM_SET_REGS _IOW(KVMIO, 0x82, struct kvm_regs)
|
|
|
|
#define KVM_GET_SREGS _IOR(KVMIO, 0x83, struct kvm_sregs)
|
|
|
|
#define KVM_SET_SREGS _IOW(KVMIO, 0x84, struct kvm_sregs)
|
|
|
|
#define KVM_TRANSLATE _IOWR(KVMIO, 0x85, struct kvm_translation)
|
|
|
|
#define KVM_INTERRUPT _IOW(KVMIO, 0x86, struct kvm_interrupt)
|
2008-12-15 05:52:10 -07:00
|
|
|
/* KVM_DEBUG_GUEST is no longer supported, use KVM_SET_GUEST_DEBUG instead */
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_DEBUG_GUEST __KVM_DEPRECATED_VCPU_W_0x87
|
2007-03-01 08:20:13 -07:00
|
|
|
#define KVM_GET_MSRS _IOWR(KVMIO, 0x88, struct kvm_msrs)
|
|
|
|
#define KVM_SET_MSRS _IOW(KVMIO, 0x89, struct kvm_msrs)
|
|
|
|
#define KVM_SET_CPUID _IOW(KVMIO, 0x8a, struct kvm_cpuid)
|
2007-03-05 10:46:05 -07:00
|
|
|
#define KVM_SET_SIGNAL_MASK _IOW(KVMIO, 0x8b, struct kvm_signal_mask)
|
2007-04-01 07:34:31 -06:00
|
|
|
#define KVM_GET_FPU _IOR(KVMIO, 0x8c, struct kvm_fpu)
|
|
|
|
#define KVM_SET_FPU _IOW(KVMIO, 0x8d, struct kvm_fpu)
|
2007-09-06 03:22:56 -06:00
|
|
|
#define KVM_GET_LAPIC _IOR(KVMIO, 0x8e, struct kvm_lapic_state)
|
|
|
|
#define KVM_SET_LAPIC _IOW(KVMIO, 0x8f, struct kvm_lapic_state)
|
2007-11-21 08:10:04 -07:00
|
|
|
#define KVM_SET_CPUID2 _IOW(KVMIO, 0x90, struct kvm_cpuid2)
|
|
|
|
#define KVM_GET_CPUID2 _IOWR(KVMIO, 0x91, struct kvm_cpuid2)
|
2007-10-22 08:50:39 -06:00
|
|
|
/* Available with KVM_CAP_VAPIC */
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_TPR_ACCESS_REPORTING _IOWR(KVMIO, 0x92, struct kvm_tpr_access_ctl)
|
2007-10-25 08:52:32 -06:00
|
|
|
/* Available with KVM_CAP_VAPIC */
|
|
|
|
#define KVM_SET_VAPIC_ADDR _IOW(KVMIO, 0x93, struct kvm_vapic_addr)
|
KVM: s390: interrupt subsystem, cpu timer, waitpsw
This patch contains the s390 interrupt subsystem (similar to in kernel apic)
including timer interrupts (similar to in-kernel-pit) and enabled wait
(similar to in kernel hlt).
In order to achieve that, this patch also introduces intercept handling
for instruction intercepts, and it implements load control instructions.
This patch introduces an ioctl KVM_S390_INTERRUPT which is valid for both
the vm file descriptors and the vcpu file descriptors. In case this ioctl is
issued against a vm file descriptor, the interrupt is considered floating.
Floating interrupts may be delivered to any virtual cpu in the configuration.
The following interrupts are supported:
SIGP STOP - interprocessor signal that stops a remote cpu
SIGP SET PREFIX - interprocessor signal that sets the prefix register of a
(stopped) remote cpu
INT EMERGENCY - interprocessor interrupt, usually used to signal need_reshed
and for smp_call_function() in the guest.
PROGRAM INT - exception during program execution such as page fault, illegal
instruction and friends
RESTART - interprocessor signal that starts a stopped cpu
INT VIRTIO - floating interrupt for virtio signalisation
INT SERVICE - floating interrupt for signalisations from the system
service processor
struct kvm_s390_interrupt, which is submitted as ioctl parameter when injecting
an interrupt, also carrys parameter data for interrupts along with the interrupt
type. Interrupts on s390 usually have a state that represents the current
operation, or identifies which device has caused the interruption on s390.
kvm_s390_handle_wait() does handle waitpsw in two flavors: in case of a
disabled wait (that is, disabled for interrupts), we exit to userspace. In case
of an enabled wait we set up a timer that equals the cpu clock comparator value
and sleep on a wait queue.
[christian: change virtio interrupt to 0x2603]
Acked-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
Signed-off-by: Carsten Otte <cotte@de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Avi Kivity <avi@qumranet.com>
2008-03-25 11:47:26 -06:00
|
|
|
/* valid for virtual machine (for floating interrupt)_and_ vcpu */
|
|
|
|
#define KVM_S390_INTERRUPT _IOW(KVMIO, 0x94, struct kvm_s390_interrupt)
|
2008-03-25 11:47:20 -06:00
|
|
|
/* store status for s390 */
|
|
|
|
#define KVM_S390_STORE_STATUS_NOADDR (-1ul)
|
|
|
|
#define KVM_S390_STORE_STATUS_PREFIXED (-2ul)
|
|
|
|
#define KVM_S390_STORE_STATUS _IOW(KVMIO, 0x95, unsigned long)
|
|
|
|
/* initial ipl psw for s390 */
|
|
|
|
#define KVM_S390_SET_INITIAL_PSW _IOW(KVMIO, 0x96, struct kvm_s390_psw)
|
|
|
|
/* initial reset for s390 */
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_S390_INITIAL_RESET _IO(KVMIO, 0x97)
|
2008-04-11 10:24:45 -06:00
|
|
|
#define KVM_GET_MP_STATE _IOR(KVMIO, 0x98, struct kvm_mp_state)
|
|
|
|
#define KVM_SET_MP_STATE _IOW(KVMIO, 0x99, struct kvm_mp_state)
|
2008-09-26 01:30:55 -06:00
|
|
|
/* Available with KVM_CAP_NMI */
|
2009-11-02 09:20:28 -07:00
|
|
|
#define KVM_NMI _IO(KVMIO, 0x9a)
|
2008-12-15 05:52:10 -07:00
|
|
|
/* Available with KVM_CAP_SET_GUEST_DEBUG */
|
|
|
|
#define KVM_SET_GUEST_DEBUG _IOW(KVMIO, 0x9b, struct kvm_guest_debug)
|
2009-05-11 02:48:15 -06:00
|
|
|
/* MCE for x86 */
|
|
|
|
#define KVM_X86_SETUP_MCE _IOW(KVMIO, 0x9c, __u64)
|
|
|
|
#define KVM_X86_GET_MCE_CAP_SUPPORTED _IOR(KVMIO, 0x9d, __u64)
|
|
|
|
#define KVM_X86_SET_MCE _IOW(KVMIO, 0x9e, struct kvm_x86_mce)
|
2009-11-02 09:20:28 -07:00
|
|
|
/* IA64 stack access */
|
2008-12-18 04:17:51 -07:00
|
|
|
#define KVM_IA64_VCPU_GET_STACK _IOR(KVMIO, 0x9a, void *)
|
|
|
|
#define KVM_IA64_VCPU_SET_STACK _IOW(KVMIO, 0x9b, void *)
|
2009-11-11 17:04:25 -07:00
|
|
|
/* Available with KVM_CAP_VCPU_EVENTS */
|
|
|
|
#define KVM_GET_VCPU_EVENTS _IOR(KVMIO, 0x9f, struct kvm_vcpu_events)
|
|
|
|
#define KVM_SET_VCPU_EVENTS _IOW(KVMIO, 0xa0, struct kvm_vcpu_events)
|
2008-07-01 15:23:49 -06:00
|
|
|
|
2009-03-12 07:45:39 -06:00
|
|
|
#define KVM_DEV_ASSIGN_ENABLE_IOMMU (1 << 0)
|
|
|
|
|
2008-07-28 10:26:26 -06:00
|
|
|
struct kvm_assigned_pci_dev {
|
|
|
|
__u32 assigned_dev_id;
|
|
|
|
__u32 busnr;
|
|
|
|
__u32 devfn;
|
|
|
|
__u32 flags;
|
2008-10-19 08:39:45 -06:00
|
|
|
union {
|
|
|
|
__u32 reserved[12];
|
|
|
|
};
|
2008-07-28 10:26:26 -06:00
|
|
|
};
|
|
|
|
|
2009-03-12 07:45:39 -06:00
|
|
|
#define KVM_DEV_IRQ_HOST_INTX (1 << 0)
|
|
|
|
#define KVM_DEV_IRQ_HOST_MSI (1 << 1)
|
|
|
|
#define KVM_DEV_IRQ_HOST_MSIX (1 << 2)
|
|
|
|
|
|
|
|
#define KVM_DEV_IRQ_GUEST_INTX (1 << 8)
|
|
|
|
#define KVM_DEV_IRQ_GUEST_MSI (1 << 9)
|
|
|
|
#define KVM_DEV_IRQ_GUEST_MSIX (1 << 10)
|
|
|
|
|
|
|
|
#define KVM_DEV_IRQ_HOST_MASK 0x00ff
|
|
|
|
#define KVM_DEV_IRQ_GUEST_MASK 0xff00
|
|
|
|
|
2008-07-28 10:26:26 -06:00
|
|
|
struct kvm_assigned_irq {
|
|
|
|
__u32 assigned_dev_id;
|
|
|
|
__u32 host_irq;
|
|
|
|
__u32 guest_irq;
|
|
|
|
__u32 flags;
|
2008-10-19 08:39:45 -06:00
|
|
|
union {
|
2008-11-23 23:32:53 -07:00
|
|
|
struct {
|
|
|
|
__u32 addr_lo;
|
|
|
|
__u32 addr_hi;
|
|
|
|
__u32 data;
|
|
|
|
} guest_msi;
|
2008-10-19 08:39:45 -06:00
|
|
|
__u32 reserved[12];
|
|
|
|
};
|
2008-07-28 10:26:26 -06:00
|
|
|
};
|
|
|
|
|
KVM: Enable MSI-X for KVM assigned device
This patch finally enable MSI-X.
What we need for MSI-X:
1. Intercept one page in MMIO region of device. So that we can get guest desired
MSI-X table and set up the real one. Now this have been done by guest, and
transfer to kernel using ioctl KVM_SET_MSIX_NR and KVM_SET_MSIX_ENTRY.
2. Information for incoming interrupt. Now one device can have more than one
interrupt, and they are all handled by one workqueue structure. So we need to
identify them. The previous patch enable gsi_msg_pending_bitmap get this done.
3. Mapping from host IRQ to guest gsi as well as guest gsi to real MSI/MSI-X
message address/data. We used same entry number for the host and guest here, so
that it's easy to find the correlated guest gsi.
What we lack for now:
1. The PCI spec said nothing can existed with MSI-X table in the same page of
MMIO region, except pending bits. The patch ignore pending bits as the first
step (so they are always 0 - no pending).
2. The PCI spec allowed to change MSI-X table dynamically. That means, the OS
can enable MSI-X, then mask one MSI-X entry, modify it, and unmask it. The patch
didn't support this, and Linux also don't work in this way.
3. The patch didn't implement MSI-X mask all and mask single entry. I would
implement the former in driver/pci/msi.c later. And for single entry, userspace
should have reposibility to handle it.
Signed-off-by: Sheng Yang <sheng@linux.intel.com>
Signed-off-by: Avi Kivity <avi@redhat.com>
2009-02-25 02:22:28 -07:00
|
|
|
|
2009-02-25 02:22:26 -07:00
|
|
|
struct kvm_assigned_msix_nr {
|
|
|
|
__u32 assigned_dev_id;
|
|
|
|
__u16 entry_nr;
|
|
|
|
__u16 padding;
|
|
|
|
};
|
|
|
|
|
2009-05-20 23:50:13 -06:00
|
|
|
#define KVM_MAX_MSIX_PER_DEV 256
|
2009-02-25 02:22:26 -07:00
|
|
|
struct kvm_assigned_msix_entry {
|
|
|
|
__u32 assigned_dev_id;
|
|
|
|
__u32 gsi;
|
|
|
|
__u16 entry; /* The index of entry in the MSI-X table */
|
|
|
|
__u16 padding[3];
|
|
|
|
};
|
|
|
|
|
2009-11-02 09:20:28 -07:00
|
|
|
#endif /* __LINUX_KVM_H */
|