> Quoting you patch (v12, because it looks slightly better, but
> the difference doesn't matter for this discussion):
>
> #define arch_vcpu_block(v) ({ \
> if ( (v)->domain->arch.hvm_domain.vmx.vcpu_block ) \
>
gt;> <feng...@intel.com>
>> Cc: Doug Goldstein <car...@cardoe.com>; Andrew Cooper
>> <andrew.coop...@citrix.com>; Dario Faggioli <dario.faggi...@citrix.com>;
>> GeorgeDunlap <george.dun...@eu.citrix.com>; Tian, Kevin
>> <kevin.t...@intel.com>
> <andrew.coop...@citrix.com>; Dario Faggioli <dario.faggi...@citrix.com>;
> GeorgeDunlap <george.dun...@eu.citrix.com>; Tian, Kevin
> <kevin.t...@intel.com>; xen-devel@lists.xen.org; Keir Fraser <k...@xen.org>
> Subject: Re: [Xen-devel] [PATCH v13 1/2]
t;kevin.t...@intel.com>; Keir Fraser <k...@xen.org>; George
> Dunlap <george.dun...@eu.citrix.com>; Andrew Cooper
> <andrew.coop...@citrix.com>; Dario Faggioli <dario.faggi...@citrix.com>; xen-
> de...@lists.xen.org
> Subject: Re: [Xen-devel] [PATCH v13 1/2] vmx
This is the core logic handling for VT-d posted-interrupts. Basically it
deals with how and when to update posted-interrupts during the following
scenarios:
- vCPU is preempted
- vCPU is slept
- vCPU is blocked
When vCPU is preempted/slept, we update the posted-interrupts during
scheduling by
