On 12/19/2011 04:11 PM, Jan Kiszka wrote:
> >>
> >> Backwards compatibility
> >
> > If we want backwards compatibility, we need more than just a simple feature
> > check, no? Oh, you feed that into CPUID? That's nifty. Ok, so you behave
> > like VMX/SVM do on real hardware - you always expose th
On 2011-12-19 15:03, Alexander Graf wrote:
>
> On 19.12.2011, at 14:59, Avi Kivity wrote:
>
>> On 12/19/2011 03:54 PM, Alexander Graf wrote:
>>> On 04.12.2011, at 19:26, Raghavendra K T wrote:
>>>
Extend the KVM Hypervisor to enable KICK_VCPU feature that allows
a vcpu to kick the halte
On 19.12.2011, at 14:59, Avi Kivity wrote:
> On 12/19/2011 03:54 PM, Alexander Graf wrote:
>> On 04.12.2011, at 19:26, Raghavendra K T wrote:
>>
>>> Extend the KVM Hypervisor to enable KICK_VCPU feature that allows
>>> a vcpu to kick the halted vcpu to continue with execution in PV ticket
>>> sp
On 12/19/2011 03:54 PM, Alexander Graf wrote:
> On 04.12.2011, at 19:26, Raghavendra K T wrote:
>
> > Extend the KVM Hypervisor to enable KICK_VCPU feature that allows
> > a vcpu to kick the halted vcpu to continue with execution in PV ticket
> > spinlock.
> >
> > Signed-off-by: Srivatsa Vaddagiri
On 04.12.2011, at 19:26, Raghavendra K T wrote:
> Extend the KVM Hypervisor to enable KICK_VCPU feature that allows
> a vcpu to kick the halted vcpu to continue with execution in PV ticket
> spinlock.
>
> Signed-off-by: Srivatsa Vaddagiri
> Signed-off-by: Raghavendra K T
> ---
> diff --git a/t
