Re: [v3 24/26] KVM: Update Posted-Interrupts Descriptor when vCPU is blocked
From: Paolo Bonzini
Date: Wed Dec 17 2014 - 12:09:59 EST
On 12/12/2014 16:14, Feng Wu wrote:
> This patch updates the Posted-Interrupts Descriptor when vCPU
> is blocked.
>
> pre-block:
> - Add the vCPU to the blocked per-CPU list
> - Clear 'SN'
Should SN be already clear (and NV set to POSTED_INTR_VECTOR)? Can it
happen that you go from sched-out to blocked without doing a sched-in first?
In fact, if this is possible, what happens if vcpu->preempted &&
vcpu->blocked?
> - Set 'NV' to POSTED_INTR_WAKEUP_VECTOR
>
> post-block:
> - Remove the vCPU from the per-CPU list
Paolo
> Signed-off-by: Feng Wu <feng.wu@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/