summaryrefslogblamecommitdiff
path: root/include/linux/kvm_para.h
blob: 3b292565a693c2363283b50fdac72880e5cca0b2 (plain) (tree) 
102d8325a1d2 ^






















































c21415e84334 ^


















102d8325a1d2 ^

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54

55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72

73






















































                                                                            

















                                                                          
      
#ifndef __LINUX_KVM_PARA_H
#define __LINUX_KVM_PARA_H

/*
 * Guest OS interface for KVM paravirtualization
 *
 * Note: this interface is totally experimental, and is certain to change
 *       as we make progress.
 */

/*
 * Per-VCPU descriptor area shared between guest and host. Writable to
 * both guest and host. Registered with the host by the guest when
 * a guest acknowledges paravirtual mode.
 *
 * NOTE: all addresses are guest-physical addresses (gpa), to make it
 * easier for the hypervisor to map between the various addresses.
 */
struct kvm_vcpu_para_state {
	/*
	 * API version information for compatibility. If there's any support
	 * mismatch (too old host trying to execute too new guest) then
	 * the host will deny entry into paravirtual mode. Any other
	 * combination (new host + old guest and new host + new guest)
	 * is supposed to work - new host versions will support all old
	 * guest API versions.
	 */
	u32 guest_version;
	u32 host_version;
	u32 size;
	u32 ret;

	/*
	 * The address of the vm exit instruction (VMCALL or VMMCALL),
	 * which the host will patch according to the CPU model the
	 * VM runs on:
	 */
	u64 hypercall_gpa;

} __attribute__ ((aligned(PAGE_SIZE)));

#define KVM_PARA_API_VERSION 1

/*
 * This is used for an RDMSR's ECX parameter to probe for a KVM host.
 * Hopefully no CPU vendor will use up this number. This is placed well
 * out of way of the typical space occupied by CPU vendors' MSR indices,
 * and we think (or at least hope) it wont be occupied in the future
 * either.
 */
#define MSR_KVM_API_MAGIC 0x87655678

#define KVM_EINVAL 1

/*
 * Hypercall calling convention:
 *
 * Each hypercall may have 0-6 parameters.
 *
 * 64-bit hypercall index is in RAX, goes from 0 to __NR_hypercalls-1
 *
 * 64-bit parameters 1-6 are in the standard gcc x86_64 calling convention
 * order: RDI, RSI, RDX, RCX, R8, R9.
 *
 * 32-bit index is EBX, parameters are: EAX, ECX, EDX, ESI, EDI, EBP.
 * (the first 3 are according to the gcc regparm calling convention)
 *
 * No registers are clobbered by the hypercall, except that the
 * return value is in RAX.
 */
#define __NR_hypercalls			0

#endif