Scott Wood 852b6d57dc kvm: add device control API ... Currently, devices that are emulated inside KVM are configured in a hardcoded manner based on an assumption that any given architecture only has one way to do it. If there's any need to access device state, it is done through inflexible one-purpose-only IOCTLs (e.g. KVM_GET/SET_LAPIC). Defining new IOCTLs for every little thing is cumbersome and depletes a limited numberspace. This API provides a mechanism to instantiate a device of a certain type, returning an ID that can be used to set/get attributes of the device. Attributes may include configuration parameters (e.g. register base address), device state, operational commands, etc. It is similar to the ONE_REG API, except that it acts on devices rather than vcpus. Both device types and individual attributes can be tested without having to create the device or get/set the attribute, without the need for separately managing enumerated capabilities. Signed-off-by: Scott Wood <scottwood@freescale.com> Signed-off-by: Alexander Graf <agraf@suse.de>		2013-04-26 20:27:20 +02:00
..
devices	kvm: add device control API	2013-04-26 20:27:20 +02:00
api.txt	kvm: add device control API	2013-04-26 20:27:20 +02:00
cpuid.txt	KVM: fix cpuid eax for KVM leaf	2012-05-06 15:51:56 +03:00
hypercalls.txt	KVM: Add documentation on hypercalls	2012-08-13 17:39:59 -03:00
locking.txt	KVM: MMU: document mmu-lock and fast page fault	2012-07-11 16:51:23 +03:00
mmu.txt	KVM: Remove unused slot_bitmap from kvm_mmu_page	2013-01-14 11:13:58 +02:00
msr.txt	KVM: clarify kvmclock documentation	2012-09-17 14:10:23 -03:00
nested-vmx.txt	KVM: nVMX: Documentation	2011-07-12 13:15:22 +03:00
ppc-pv.txt	KVM: Add ppc hypercall documentation	2012-08-13 17:39:59 -03:00
review-checklist.txt	Correct occurrences of	2011-05-06 09:27:55 -07:00
timekeeping.txt