Re: [PATCH 1/3] KVM: add spinlock-exiting optimize framework

2017-08-07 Thread Longpeng (Mike)
On 2017/8/7 16:55, David Hildenbrand wrote: > On 07.08.2017 10:44, Longpeng(Mike) wrote: >> If the vcpu(me) exit due to request a usermode spinlock, then >> the spinlock-holder may be preempted in usermode or kernmode. >> >> But if the vcpu(me) is in kernmode, then the holder must be >> preempte

Re: [PATCH 1/3] KVM: add spinlock-exiting optimize framework

2017-08-07 Thread David Hildenbrand
On 07.08.2017 10:44, Longpeng(Mike) wrote: > If the vcpu(me) exit due to request a usermode spinlock, then > the spinlock-holder may be preempted in usermode or kernmode. > > But if the vcpu(me) is in kernmode, then the holder must be > preempted in kernmode, so we should choose a vcpu in kernmode

[PATCH 1/3] KVM: add spinlock-exiting optimize framework

2017-08-07 Thread Longpeng(Mike)
If the vcpu(me) exit due to request a usermode spinlock, then the spinlock-holder may be preempted in usermode or kernmode. But if the vcpu(me) is in kernmode, then the holder must be preempted in kernmode, so we should choose a vcpu in kernmode as the most eligible candidate. For some architectu