Re: [PATCH 13/21] KVM: Add support for enabling capabilities per-vcpu

2010-04-01 Thread Alexander Graf
On 01.04.2010, at 10:51, Avi Kivity wrote: On 03/24/2010 10:48 PM, Alexander Graf wrote: Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch. In order to have a generic mechanism in how to

Re: [PATCH 13/21] KVM: Add support for enabling capabilities per-vcpu

2010-04-01 Thread Avi Kivity
On 04/01/2010 12:06 PM, Alexander Graf wrote: On 01.04.2010, at 10:51, Avi Kivity wrote: On 03/24/2010 10:48 PM, Alexander Graf wrote: Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next

Re: [PATCH 13/21] KVM: Add support for enabling capabilities per-vcpu

2010-04-01 Thread Avi Kivity
On 03/24/2010 10:48 PM, Alexander Graf wrote: Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch. In order to have a generic mechanism in how to enable capabilities individually, this patch

[PATCH 13/21] KVM: Add support for enabling capabilities per-vcpu

2010-03-24 Thread Alexander Graf
Some times we don't want all capabilities to be available to all our vcpus. One example for that is the OSI interface, implemented in the next patch. In order to have a generic mechanism in how to enable capabilities individually, this patch introduces a new ioctl that can be used for this