Re: [patch 0/3] KVM KVM_HC_RT_PRIO hypercall support

2017-09-27 Thread Marcelo Tosatti
On Fri, Sep 22, 2017 at 08:23:02AM +0200, Jan Kiszka wrote: > On 2017-09-22 03:19, Marcelo Tosatti wrote: > > On Thu, Sep 21, 2017 at 07:45:32PM +0200, Jan Kiszka wrote: > >> On 2017-09-21 13:38, Marcelo Tosatti wrote: > >>> When executing guest vcpu-0 with FIFO:1 priority, which is necessary to >

Re: [patch 0/3] KVM KVM_HC_RT_PRIO hypercall support

2017-09-21 Thread Jan Kiszka
On 2017-09-22 03:19, Marcelo Tosatti wrote: > On Thu, Sep 21, 2017 at 07:45:32PM +0200, Jan Kiszka wrote: >> On 2017-09-21 13:38, Marcelo Tosatti wrote: >>> When executing guest vcpu-0 with FIFO:1 priority, which is necessary to >>> deal with the following situation: >>> >>> VCPU-0 (housekeeping VC

Re: [patch 0/3] KVM KVM_HC_RT_PRIO hypercall support

2017-09-21 Thread Marcelo Tosatti
On Thu, Sep 21, 2017 at 07:45:32PM +0200, Jan Kiszka wrote: > On 2017-09-21 13:38, Marcelo Tosatti wrote: > > When executing guest vcpu-0 with FIFO:1 priority, which is necessary to > > deal with the following situation: > > > > VCPU-0 (housekeeping VCPU) VCPU-1 (realtime VCPU) > > >

Re: [patch 0/3] KVM KVM_HC_RT_PRIO hypercall support

2017-09-21 Thread Jan Kiszka
On 2017-09-21 13:38, Marcelo Tosatti wrote: > When executing guest vcpu-0 with FIFO:1 priority, which is necessary to > deal with the following situation: > > VCPU-0 (housekeeping VCPU) VCPU-1 (realtime VCPU) > > raw_spin_lock(A) > interrupted, schedule task T-1 raw_spin_loc