>On 12.12.2015 at 9:22pm, <quan...@intel.com> wrote: > This patches are based on Kevin Tian's previous discussion 'Revisit VT-d > asynchronous flush issue'. > Fix current timeout concern and also allow limited ATS support in a light way:
> 2. Fix vt-d flush timeout issue. > > If IOTLB/Context/IETC flush is timeout, we should think all devices under > this IOMMU cannot function correctly. > So for each device under this IOMMU we'll mark it as unassignable and kill > the domain owning the device. > Any comment for this point? Instead of panic, is it enough? -Quan > If Device-TLB flush is timeout, we'll mark the target ATS device as > unassignable and kill the domain owning > this device. > > If impacted domain is hardware domain, just throw out a warning. It's an > open here whether we want to kill > hardware domain (or directly panic hypervisor). Comments are welcomed. > > Device marked as unassignable will be disallowed to be further assigned to > any domain. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
