> -----Original Message----- > From: Tian, Kevin > Sent: Friday, November 18, 2016 11:03 AM > To: Wu, Feng <feng...@intel.com>; xen-devel@lists.xen.org > Cc: jbeul...@suse.com; andrew.coop...@citrix.com; > george.dun...@eu.citrix.com; dario.faggi...@citrix.com > Subject: RE: [PATCH v8 0/7] VMX: Properly handle pi descriptor and per-cpu > blocking list > > > From: Wu, Feng > > Sent: Friday, November 18, 2016 9:57 AM > > > > The current VT-d PI related code may operate incorrectly in the > > following scenarios: > > 1. When the last assigned device is dettached from the domain, all > > the PI related hooks are removed then, however, the vCPU can be > > blocked, switched to another pCPU, etc, all without the aware of > > PI. After the next time we attach another device to the domain, > > which makes the PI realted hooks avaliable again, the status > > of the pi descriptor is not true. Beside that, the blocking vcpu > > may still remain in the per-cpu blocking in this case. Patch [1/7] > > and [2/7] handle this. > > > > 2. [4/7] unify the code path of PI mode update and remapped mode update > > > > 2. When IRTE is in posted mode, we don't need to set the irq > > affinity for it, since the destination of these interrupts is > > vCPU and the vCPU affinity is set during vCPU scheduling. Patch > > [5/7] handles this. > > > > 4. [6/7] is a cleanup patch > > > > 5. When a pCPU is unplugged, and there might be vCPUs on its > > list. Since the pCPU is offline, those vCPUs might not be woken > > up again. [7/7] addresses it. > > > > > > just for completeness you didn't introduce 3/7 here.
Okay, maybe I need add it. Thanks, Feng _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
