[BACK]Return to kvm_para.h CVS log [TXT][DIR] Up to [Development] / linux-2.6-xfs / include / linux

File: [Development] / linux-2.6-xfs / include / linux / kvm_para.h (download)

Revision 1.1, Tue Mar 20 15:37:21 2007 UTC (10 years, 7 months ago) by tes.longdrop.melbourne.sgi.com
Branch: MAIN

Merge up to 2.6.21-rc4
Merge of 2.6.x-xfs-melb:linux:28276b by kenmcd.

#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